srrrse
srrrse
@JelteF Sorry, I was accidentally not watching this repo, so I didn't get notified about your issue! I'm open to having this in derive_more - most of all I'm very...
There's an open PR already in rust-lang-nursery/failure#179
Yea, this code was moved into the main repo. I'll shut this repo down once failure 1.0 is released.
That's an interesting idea! But right now we enable you to write a custom Display impl if you don't have the attribute. How would still support that use case? Maybe...
This is definitely because of the const you're trying to use, I would like to support consts and suspect its possible, I'm re-opening to track investigating consts in the display...
This is an unfortunate limitation of the rustc attribute syntax; once attributes are more flexible, I intend to make this work more like how you would expect it to (`self.0`...
> failure had a really nice Error + ErrorKind model. How do we define custom errors with Fehler? (though perhaps it's not even in scope, might be worth mentioning?) I...
It's very easy to wipe away the boilerplate. Pretty sure if the user just defines `MyErrorKind` themselves they just need to pick a name for `MyError`: ```rust error_with_kind! { MyError...
That's exactly what failure's `Context` type was, it was only recommended to create a new type since it'd be part of your public API
Yep, I just haven't yet bothered implementing it because stmt_expr_attributes etc are unstable features.