KITFORMA · EDITORIAL ANSWER
Does the classic loop-variable capture bug still apply under Go 1.22 semantics?
KitForma editorial guide. It depends on language-version semantics and how the variable is declared. Go 1.22 changed eligible loop-declared variables to per-iteration variables; an outer variable reused by assignment is different.
Step-by-step answer
It depends on language-version semantics and how the variable is declared. Go 1.22 changed eligible loop-declared variables to per-iteration variables; an outer variable reused by assignment is different.
Record the module go directive and toolchain before applying old advice. Passing the iteration value as a goroutine parameter can make intent clear across versions. Shared pointed-to data still needs its own synchronization.
Test callbacks after loop completion, avoiding scheduling luck. The language change does not repair every captured outer variable or mutable pointee. Treat historical examples as version-specific evidence, not proof of a current universal Go bug.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.