Arnav Singh

Not by me. - `error-chain` itself has been abandoned (again). - Most new users don't know `derive-error-chain` exists, so they compare `error-chain` with `failure` and go with `failure` (and rightly...

`failure` is fine for now.

What I said [here](https://github.com/Arnavion/derive-error-chain/issues/5#issuecomment-261841278) is still mostly true. Compared to the `error_chain!` macro, here the user needs to declare an enum, remember to mark it `pub`, remember to derive `Debug`,...

It might be possible.

(I should clarify that I think it might be possible, not that it's a good idea. It seems unnecessarily roundabout for a regular macro to generate input for another proc...

An update to my earlier sentiments, based on the last few months: >That repo [Arnavion/fac-rs] is probably the only bunch of crates that use it. I've not heard of anyone...

It's documented, but admittedly not in a place where you'd look. https://github.com/Arnavion/derive-error-chain/blame/741135fc0ef00b204e6661eb283ead6e28fc7fb3/CHANGELOG.md#L60 Making error-chain a dependency of this crate will not work. It needs to be a dependency of the...

Using error-chain's traits is a deliberate decision. https://github.com/Arnavion/derive-error-chain/issues/5

I've fixed the whitespace errors, missing impl for `serde_json::Value`, wrong reference to the trait in the templates, incorrect impls of the trait for borrowed types, etc etc in [pr/121.](https://github.com/Arnavion/k8s-openapi/compare/pr/121) ---...

Yes, it's on my plate. I've just been busy myself.