As most people around here, I would prefer avoiding #2 and its magic variable, unless we can wrap it in a nice syntax extension/macro.
Between #1 and #3, I prefer #1 for the exact reason James Boyden dislikes it: it lets me concentrate on the most common path, without having to deal with low-level issues upfront. I believe that this makes both writing and reading algorithms easier. I would also like to see a more complete example. 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? But, once again, I like the shape of things. Thanks, David
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
