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.

Sign up for GitHub

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

Jump to bottom

Figure out error handling #7

Closed

VorpalBlade opened this issue Feb 29, 2024 · 1 comment

Labels

Owner

VorpalBlade commented Feb 29, 2024

Currently using anyhow. Not ideal in a library (also no serde support).

Requirements:

Painless inclusion of backtraces (on stable), including for nested causes (thiserror fails this).
Ability to use errors as the associated type in TryFrom etc (error-stack fails this).
Ability to convert existing code one step at a time (error-stack fails this, no backtraces for you until you convert everything)
Support for type erased errors where it makes sense

The text was updated successfully, but these errors were encountered:

VorpalBlade added the C-enhancement label

VorpalBlade mentioned this issue

Output options #3

Open

3 tasks

Owner Author

VorpalBlade commented Jul 22, 2024

Will continue to use anyhow except for where errors need to be programatically handled.

VorpalBlade closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment