fix: fix referencing the loop variable and avoid slice grow #226
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.
The semantics of for loop variables is controlled by the language version in the module’s go.mod file when using go version 1.22 or later. That is it works well when the version in go module is 1.22 or later. Otherwise the reference using pointer will capture the same loop variable.
In addition, making slice with length avoids slice growing to ensure fairness.
References: