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.

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

Better errors #33

Open
bitfl0wer opened this issue May 16, 2024 · 0 comments
Open

Better errors #33

bitfl0wer opened this issue May 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bitfl0wer
Copy link
Member

The current state of error-handling in this crate is, well, okay. What bugs me a lot is how unclear certain error messages are.
Example:

thread 'main' panicked at tests/blubb.rs:66:14: called Result::unwrap() on an Err value: InvalidInput(Malformed("Expected BitString, found SEQUENCE"))

This does not really tell me much. It's lacking information about at least the file and function/method this error occurred in. It would be nice if error messages could be enriched with this information in a nice way.
@bitfl0wer bitfl0wer added the enhancement New feature or request label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bitfl0wer