On 1/31/13 3:41 PM, Brian Anderson wrote:
There's also the problem with failure after switching stacks. Right now
there is a guard in the stack switch that catches exceptions thrown by
foreign code and aborts the process, which makes this bogus:

do stackswitch {
   fail;
}

We could remove that guard and leave the behavior undefined ...

Could we implement unsafe `catch` to make this work? Then the stack switching code could catch the failure and abort.

The scheduler probably needs the ability to catch anyway, right?

Patrick

_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to