Loop variables and toolchain semantics

It depends on how the variable is declared and on the language version used by the module. Modern Go changed semantics for loop-declared iteration variables; repeating the old universal capture warning is inaccurate.

A variable declared outside the loop and assigned by the loop can still be shared across iterations. Shared pointed-to objects and other mutable fixtures also remain shared even when each iteration variable is distinct.

Inspect the go directive and actual declaration, then write explicit ownership where it improves clarity. Passing a value as a goroutine argument can make the captured value obvious, but does not deep-copy referenced data or provide a join.