We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
return" statements should not occur in "finally" blocks.
This rule raises an issue when a jump statement (break, continue, return, throw, and goto) would force control flow to leave a finally block.
The finally block is always executed after everything else. It'll override the return statement present in 'try' or 'catch' blocks.
More information in 'Don't return in finally clause' and 'The Java Hall of #Shame'.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
return" statements should not occur in "finally" blocks.
This rule raises an issue when a jump statement (break, continue, return, throw, and goto) would force control flow to leave a finally block.
The finally block is always executed after everything else. It'll override the return statement present in 'try' or 'catch' blocks.
More information in 'Don't return in finally clause' and 'The Java Hall of #Shame'.
The text was updated successfully, but these errors were encountered: