-
Notifications
You must be signed in to change notification settings - Fork 376
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
Adding catch_panic anti-pattern #109
base: main
Are you sure you want to change the base?
Conversation
da9e732
to
9c738a6
Compare
Isn't web frameworks doing this? Is this really an anti-pattern? |
In the "advantages" section it is mentioned |
We can take a lot from the official documentation: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html |
33674b9
to
8871ccb
Compare
Co-authored-by: Marco Ieni <11428655+MarcoIeni@users.noreply.github.com>
b61bee8
to
9e2651a
Compare
@MarcoIeni
|
By default it expects the style to be consistent, see this Since there is a |
ah ok, then it's nice! just didn't see the plus and the error message was not so helpful as i'm used to from rustc :D |
We only see what's bad, is there something that could be done instead of this pattern, if there is maybe we should show it. |
As this anti-pattern is focussed on "using a method that catches unexpected problems (implementation bugs) for handling an expected problem, such as a missing file.", Imho EDIT: So a link to the error handling chapter on the rust book could be sufficient? Not sure, but open for your ideas. :) |
I think that is an option but at least not so easy to pickup, but at least we have some suggestions. I am not aware of any straightforward switch. |
Due to inactivity of the author and maintainers not being able to edit the PR I'll move #22 to a new branch in this repository.
Future fixes to the PR will be made on this branch.