Fixing For Loops in Go 1.22

[NewsBot]

A new Go blog post/announcement has been posted!

<div class="Article" data-slug="/blog/loopvar-preview">

<h1 class="small"><a href="/blog/">The Go Blog</a></h1>


<h1>Fixing For Loops in Go 1.22</h1>
  
  <p class="author">
  David Chase and Russ Cox<br>
  19 September 2023
  </p>
  
  <p>Go 1.21 includes a preview of a change to <code>for</code> loop scoping

that we plan to ship in Go 1.22,
removing one the most common Go mistakes.

The Problem

If you’ve written any amount of Go code, you’ve probably made the mistake of keeping a reference to a loop variable past the end of its iteration, at which point it takes on a new value that you didn’t want. For example, consider this program:

func main() {
    done := make(chan bool)
values := []string{"a", "b", "c"}
for _, v := range values {
    go func() {
        fmt.Println(v)
      ...

Get the full details here: Fixing For Loops in Go 1.22 - The Go Programming Language