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
In Go 1.22 (with GOEXPERIMENT=loopvar now the default), the Range statement for test <test> does not reinitialise the variable <var> linter is no longer accurate. If you take the example program linked from https://github.com/kunwardeep/paralleltest?tab=readme-ov-file#tparallel-is-called-in-the-range-method-and-test-case-variable-tc-being-used-but-is-not-reinitialised-more-info, you can see that it no longer reports incorrect output.
GOEXPERIMENT=loopvar
Range statement for test <test> does not reinitialise the variable <var>
Is it possible to omit these warnings when running on Go 1.22+ or allow a mechanism to ignore these warnings?
The text was updated successfully, but these errors were encountered:
Hey @pkwarren, thanks for bringing this to my attention. Any chance you could submit a PR?
Sorry, something went wrong.
@kunwardeep I create a PR to add an option #35
Successfully merging a pull request may close this issue.
In Go 1.22 (with
GOEXPERIMENT=loopvar
now the default), theRange statement for test <test> does not reinitialise the variable <var>
linter is no longer accurate. If you take the example program linked from https://github.com/kunwardeep/paralleltest?tab=readme-ov-file#tparallel-is-called-in-the-range-method-and-test-case-variable-tc-being-used-but-is-not-reinitialised-more-info, you can see that it no longer reports incorrect output.Is it possible to omit these warnings when running on Go 1.22+ or allow a mechanism to ignore these warnings?
The text was updated successfully, but these errors were encountered: