Move from error-chain to failure

[ufoscout]

As error-chain is currently deprecated ( rust-lang-deprecated/failure#181 ), I would propose to move to failure which is lots of traction in the rust community.

[Keats]

Failure is not currently actively maintained so it's more likely this crate will switch back to using plain Error for the next major version when a new ring version is released. On 13 Jul 2018 12:12, "Francesco" <notifications@github.com> wrote: As error-chain is currently deprecated ( rust-lang-deprecated/failure#181 <rust-lang-deprecated/failure#181> ), I would propose to move to failure which is lots of traction in the rust community. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#57>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApho36M9jgvVwzyNsBDpqOVZZYQBXO9ks5uGHKUgaJpZM4VOpQe> .

[ufoscout]

@Keats

oh, sorry, for what I read I thought 'failure' was going to be the default way of handling errors in rust.
I am still a newbie in rust and I am having troubles with this simple piece of code:

    pub fn generate(&self) -> Result<String, failure::Error> {
        jsonwebtoken::encode(&self.header_default, &my_claims, &self.secret.as_ref())
    }

I use failure and I am not able to integrate the result of the jsonwebtoken::encode call with the rest of my code, the compilation fails with:

expected struct `failure::Error`, found struct `core::jwt::jsonwebtoken::errors::Error`

but I don't want to return errors that do not match the failure::Error trait, do you have any suggestion? Is there any simple way to convert from core::jwt::jsonwebtoken::errors::Error to failure::Error?

[Keats]

can you do something like .map_err(|err| err.into()) to convert errors from one to the other?

[Keats]

Remove error chain in favour of plain Error