Chore: prefer smaller scope for variables in codebase #9265
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.
What is the purpose of this pull request? (put an "X" next to item)
[x] Other, please explain:
What changes did you make? (Give an overview)
I made an attempt at implementing the
prefer-smaller-scope
rule proposal, which was originally proposed in #5284. That attempt can be found here.Unfortunately, I found that the rule would incorrectly report some places where declaring a variable in an outer scope is necessary if an inner scope is executed multiple times. I don't know of a good way to avoid those false positives while still keeping the rule useful.
However, by implementing the rule I found a number of cases where we can reduce the scope of the variables.
Is there anything you'd like reviewers to focus on?
Nothing in particular