-
Notifications
You must be signed in to change notification settings - Fork 13
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
Lessen amount of panics #59
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hasezoey, this looks good to me but I agree -- we should make backtrace a default feature
rebased because i noticed some problems. mainly that the function was PS: also removed |
rebased on latest main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, looks good to me 👍
Feel free to merge this in, but if you have the time, I'd love to remove the 'backtrace' feature flag and just make it the default (no feature checks) |
i have it made behind a feature flag that so that if the library part is used it can be configured, also because backtrace for errors is not quite standardized yet, see: |
this includes "panic!" and "expect" and some "unwrap" feat(lib): replace panics with results feat(parser): replace panics with results feat(file): replace panics with results
This PR changes to use
Result
wherever possible and so lessen the amount ofpanic!
,unwrap
andexpect
sre #56
should feature
backtrace
maybe be adefault
?