These are chat archives for rust-lang/rust
error-chainwas promoted before, and now suddenly it's madness and we should use
failure. I'm not convinced
failurewill be the last error handling story in Rust.
failuredoes not handle localization too well, does it?
error-chainwere clear from the get go, esp. the heavy use of macros. Those weren't lessons one could only learn from experience. Now
failureis released by another team member of Rust, but I haven't noticed a broad consultation on its design. Perhaps I've missed it, but perhaps that says enough, since I happen to enjoy following Rust developments every day.
failurerepresents an evolution. It seems to me it does. But it is a lot to ask developers to rewrite error handling code all over (maybe not necessarily, but ideally yes).
0.1.0, so it is exactly in the phase of gathering feedback for initial design. This evolution path is pretty similar to that of the futures crate, for example.
::std::error::Errorhas broken design, and that's kinda tough to fix.
failure in my opinion aims to be the long term solution/the new std error, but we'll need to see, as a community, how well it works in practice. The migration will be painful though, but it's not obvious how to avoid it :(
About consensus, yeah, there weren't any RFC yet, but it's a crates.io crate, so it is much easier to experiment with without RFCs
Hm, I didn't get the impression (from the presentation by @withoutboats) that
failure is necessary set to replace the standard library Error... Only time an experience will tell :) But it has pretty good chances though: the design seem really solid
For clippy, there's dev-tools IRC I guess: https://kiwiirc.com/client/irc.mozilla.org/#rust-dev-tools