These are chat archives for rust-lang/rust
@fungos The problem is that a library can't solve the problem of implicitly converting your custom type to an
failure::Error. What it can and does do is support
throw!(fail); for working with
I still feel like
failure has value over the existing
trait Error ecosystem:
no_stdand other trait fixes
causein the trait.
failure_deriveis a much better way of creating errors than error-chain
Contextis a nice way to do quick and dirty error reporting and chaining
But yes, I feel like some renaming, reorganizing, filling in a couple holes, and some improved docs would make the experience more straight forward / less confusing.