Skip to content
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

[0.16] Move off error_chain #108

Open
kw217 opened this issue Jan 18, 2021 · 2 comments
Open

[0.16] Move off error_chain #108

kw217 opened this issue Jan 18, 2021 · 2 comments
Labels
enhancement help wanted improved-api Work towards a 1.0 release (initially 0.18)

Comments

@kw217
Copy link
Collaborator

kw217 commented Jan 18, 2021

error_chain was great, but it's a bit outdated now. We should move to anyhow/thiserror or other modern error approach.

@kw217 kw217 added enhancement help wanted improved-api Work towards a 1.0 release (initially 0.18) labels May 25, 2021
@zihadmahiuddin
Copy link

zihadmahiuddin commented Jul 16, 2022

I've just started trying this library and noticed that I can't use the ? operator with the Result type I normally use in my projects (which comes from eyre). I get errors saying some Error type (one defined by the error_chain macro I assume) doesn't implement the Sync trait.
What do you think about using eyre? Or maybe error-stack once it's possible to use without the nightly toolchain.

EDIT: Now that I think about it, it might not be a lot more beneficial to use eyre over anyhow so maybe that will be just fine.

@kw217
Copy link
Collaborator Author

kw217 commented Aug 4, 2022

Error handling is still quite an active area in Rust; whoever picks this up should take a careful look at the landscape before choosing a library. It should be mature and widely used, and ideally on track to becoming (de-facto) "standard".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement help wanted improved-api Work towards a 1.0 release (initially 0.18)
Projects
None yet
Development

No branches or pull requests

2 participants