-
Notifications
You must be signed in to change notification settings - Fork 282
Add section warning against catching Throwables #264
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
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I agree with the advice Noah wants to add here (even tho' I'm guilty of catching Throwable
myself).
BTW, I've fixed the codespell failure on the main branch (ignore rouge
).
@NoahTheDuke
NoahTheDuke
force-pushed
the
nb/catching-throwables
branch
from
July 15, 2025 17:36
51257cc
to
ee87d55
Compare
I rebased on master to fix the spelling mistake.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
I've noticed that many Clojure programmers use
(catch Throwable t ...)
as a means of not dealing with Exceptions. However, this is poor Java practice given that Errors are generally treated as "the application should fail" situations. As such, I think it would be nice to have a recommendation against using(catch Throwable t ...)
alongside a nudge towards using explicit Error and Exception classes in catch clauses.cf: Blind Rescues in the Ruby Style Guide, the recommendation of the Java Docs on Errors.