On 10/23/12 10:01 PM, Graydon Hoare wrote: > On 12-10-23 08:30 AM, David Rajchenbach-Teller wrote: > >> Finally, I would like to be sure that I understand one thing: as far as >> I understand, this mechanism is not designed to handle any kind of >> concurrent condition, i.e. a condition raised in one task and best >> handled in another. The mechanism intended to handle such conditions is >> task failure. Am I correct? > > Well, raise() is just a normal, synchronous call to a handler. The > handler is free to do things like, say, send a message and wait for a > response from a supervisor task, before continuing.
Good point. I imagine that we will see nice applications to this. Cheers, David -- David Rajchenbach-Teller, PhD Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
