unhide BareExcept warnings and make them errors #7164
Merged
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
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.
In the couple of years since:
BareExceptwarnings #4660BareExceptwarnings #4661BareExceptwarnings #4755And maybe as a result of updating to Nim 2.2, these warnings appear to have vanished entirely.
There are, for the moment, some remaining localized use cases for them, such as test runners where arguably it's worth dealing with its not being architecturally defined anymore to keep the test framework robust, but in general those can be addressed by locally disabling this warning specifically there.