You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
anyhow:error as a "catch-all" error type is not ideal as it means throwing away the benefit gained from rusts native error handling and type system which enable great error quality with little added boilerplate code.
Describe alternatives you've considered
There is the alternative of manually building the error types and not using any crate at all but I don't see much of a reason for that.
There might be some other crates better suited for this specific job but I am not aware of any.
The text was updated successfully, but these errors were encountered:
I'd say we need to split off "library"-ish code in mehari and annonars and use this error there first. This will probably come with some structural changes in these repositories, conversion into workspaces/split into smaller crates.
Is your feature request related to a problem? Please describe.
anyhow:error as a "catch-all" error type is not ideal as it means throwing away the benefit gained from rusts native error handling and type system which enable great error quality with little added boilerplate code.
Describe the solution you'd like
https://docs.rs/thiserror/latest/thiserror/ < is my personal choice of crates for this purpose however there are others.
Describe alternatives you've considered
There is the alternative of manually building the error types and not using any crate at all but I don't see much of a reason for that.
There might be some other crates better suited for this specific job but I am not aware of any.
The text was updated successfully, but these errors were encountered: