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

Error Handling #55

Open
Swiftb0y opened this issue Feb 27, 2022 · 1 comment
Open

Error Handling #55

Swiftb0y opened this issue Feb 27, 2022 · 1 comment

Comments

@Swiftb0y
Copy link
Contributor

We should think about proper error handling facilities. Currently we are just passing along the errors that our parser libraries (nom, binrw) generate. IMO these are dependencies that should not appear in public interface, since that forces a hard transitive dependency for the library consumer, which in turn would make changing internals (restructuring parsing/serialization) a breaking change.

https://blog.yoshuawuyts.com/error-handling-survey/
https://nick.groenen.me/posts/rust-error-handling/

@Swiftb0y
Copy link
Contributor Author

also see this very good post:
https://www.unwoundstack.com/blog/rust-error-handling.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant