Implemented a new constructor for Error: from_err()

[golddranks]

from_err() chains another error as the cause of Error.

Another thing to consider is that currently the Error::from_kind() and Error::form_err() constructors take the kind directly. Since this is a ergonomics-oriented library, it might be reasonable to take Into<ErrorKind>? What do you think? Or will it cause inference problems again?

[Yamakaky]

Seems good. Could you add tests?

[golddranks]

Yes, but I don't have time and energy to do it now. If you want to, go ahead. If you don't, I'll see what I can do in the following days.

[golddranks]

Ok, here's a test.

[Yamakaky]

Seems good. One cosmetic change though: what about from_chain or with_chain instead? from_err can be confused with From<Error>.

[golddranks]

Ah, indeed. with_chain seem to be in line with some other ecosystem names. I'll change it to that.

Another thing: What do you think of taking Into<ErrorKind> instead of ErrorKind?

[Yamakaky]

That would be better.

[golddranks]

All right, made the changes.

[Yamakaky]

Sorry, I forgot: could you also update the changelog and add an example in the doc?

[golddranks]

I'll do that tomorrow.

[golddranks]

Sorry for the delay. I'll do the things starting now.

[golddranks]

The other constructor on Error, from_kind doesn't have examples either. Besides, I'm unsure if you meant adding them to the ChainedError trait or for the generated example. Or on the main page. What kind of example were you thinking of?

[Yamakaky]

Yeah, seems good.
Before merge, could you put the trait constraints into the where condition? These lines are way too long ^^

[golddranks]

Done!

[Yamakaky]

Thanks a lot!