-
Notifications
You must be signed in to change notification settings - Fork 1
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
enh: Error handling #175
Comments
good point for usability. I'll use this issue to gather relevant data. I'll ignore items from examples / benches since those don't affect the library. |
explicit panics, expectsIgnoring unreachable panics. panics
expects
|
unwraps (fixed)I removed unwrap from type conversion / cast, as well as unwrap from tests.
|
non-crashingwarnings
Result in returns
|
I've come up with a list of principles that can be used to determine what should be done about a given problem at execution
With these rules:
From there, we can:
Additionally, I can use the @cedricchevalier19 we can talk about this approach today, as well as #172 |
Discuss and design a coherent error handling.
Information
Suggested changes
Current state
There are:
Error
typespanic
orunimplemented
See #169, #174
Proposal
I'd appreciate it if you could find a coherent way to deal with different errors. It should be lightweight, but it should be thought out thoroughly to make honeycomb usable as a library.
The text was updated successfully, but these errors were encountered: