ssa: modernize go for variables (forvar) #1073
Open
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.
Today I saw this message in my IDE:
Then I found this:
https://go.dev/doc/go1.22#language
Starting with Go 1.22, for variables are recreated on every iteration, instead of being created only once in the beginning and then updated.
I have used this variable copy+shadowing many times before inside loops and understand why this was needed before Go 1.22, so I'm glad to learn about this improvement.
This language improvement also eliminates the need for this pattern (which also exists in a few places in our codebase):