Remove unnecessary closure variable reassignments #125
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.
This pull request primarily removes unnecessary variable reassignments in range loops throughout the codebase, which were previously used to avoid closure capture issues in goroutines and subtests. These changes simplify the code and rely on Go's improved handling of range variable capture since Go 1.22.
Additionally, a new linter is enabled to help catch potential issues with loop variables in the future.
Linter configuration
copyloopvarlinter in.golangci.ymlto help detect incorrect usage of loop variables in closures.Code cleanup and simplification
var := var) in test files and goroutine closures.