New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: In src/errors.rs, why are ContextualErrorKind and ContextualError declared separately? #87
Comments
It's this pattern: https://rust-lang-nursery.github.io/failure/error-errorkind.html |
Given its high maintenance cost, and its convoluted usage ( |
@boastful-squirrel did this part so maybe they can provide some insight here. |
That's from when I was using The reason I didn't remove the So if @svenstaro agrees, we could totally drop those calls everywhere. If so, should I include that in my current PR ? While I'm a it... Or another one ? EDIT: you already did it, cool |
In that case, sure, go ahead.
…On Sat, Apr 27, 2019, 11:43 Boastful Squirrel ***@***.***> wrote:
That's from when I was using failure's context() method, see the link
that @svenstaro <https://github.com/svenstaro> posted. Now that I don't
use the context() feature anymore, all methods could return a
ContextualErrorKind and you could simply write ContextualErrorKind::<name>
everywhere.
The reason I didn't remove the ContextualError type yet is because I keep
playing with failure to see if there is a way to have the errors the way
they are now, but well, still not yet.
So if @svenstaro <https://github.com/svenstaro> agrees, we could totally
drop those calls everywhere.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAANAHYQNX34JRAFFD5N5LPSQN4JANCNFSM4HI3SZ3A>
.
|
In
src/errors.rs
, I seeContextualError
being a wrapper ofContextualErrorKind
, is there a reason of this?The text was updated successfully, but these errors were encountered: