+1 here too. I agree with what Alex said about conditions. They're useful for when you can actually recover from the error gracefully, but for generic error reporting they're kind of a PITA.
-Kevin On Oct 16, 2013, at 11:16 AM, Patrick Walton <pwal...@mozilla.com> wrote: > On 10/16/13 11:02 AM, Alex Crichton wrote: >> All that being said, we're not making much progress without an idea of where >> to >> possibly go next. Right now, the current idea is to create an Error trait and >> have I/O operations return Result<T, ~Error> instead of Option<T>. This would >> mean that Reader/Writer and other associated traits would be defined for >> Result<T, ~Error> where T: Trait (so you could still chain operations >> easily), >> and you could very easily check for an I/O error. > > +1 for the use of Result. Yay monads! > > Patrick > > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
