Is your feature request related to a problem? Please describe.
For some reason EmptyCatchBlock special-cases InterruptedException and CloneNotSupportedException. Catch blocks are already ignored if the exception is named ignored or expected, which is nice as it signals to the reader that the empty catch block was not a mistake. I think this holds even for those exception types, and code would be clearer if they were not special-cases. Besides, this particularity was not documented.
Describe the solution you'd like
Remove those special cases and make EmptyCatchBlock flag InterruptedException and CloneNotSupportedException just the same as other exception types
Describe alternatives you've considered
None
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4