Reputation: 231
I have this code. I expect to output:
hello : 1
world : 2
but it outputs:
world : 2
world : 2
Is there something wrong with my code?
package main
import (
"fmt"
"time"
)
type Task struct {
name string
data int32
}
func (this *Task) PrintData() {
fmt.Println(this.name, ":", this.data)
}
func main() {
tasks := []Task{{"hello", 1}, {"world", 2}}
for _, task := range tasks {
go task.PrintData()
}
time.Sleep(time.Second * 5000)
}
Upvotes: 7
Views: 7993
Reputation: 121169
Because PrintData
is a pointer receiver and task
is a value, the compiler automatically takes the address of task
when making the method call. The resulting call is the same as (&task).PrintData()
.
The variable task
is set to a different value on each iteration through the loop. The first goroutine doesn't run until task
is set to second value. Run this example to see that the same address is passed to PrintData on each iteration.
There are a few ways to fix this. The first is to use *Task
in the slice:
tasks := []*Task{{"hello", 1}, {"world", 2}}
for _, task := range tasks {
go task.PrintData()
}
The second is to create a new variable inside the loop:
tasks := []Task{{"hello", 1}, {"world", 2}}
for _, task := range tasks {
task := task
go task.PrintData()
}
A third is to take the address of the slice element (using the automatically inserted address operation):
tasks := []Task{{"hello", 1}, {"world", 2}}
for i := range tasks {
go tasks[i].PrintData()
}
Yet another option is to change PrintData to a value receiver to prevent the method call from automatically taking the address of task
:
func (this Task) PrintData() {
fmt.Println(this.name, ":", this.data)
}
This issue is similar to the issue discussed in the closures and goroutines FAQ. The difference between the issues is the mechanism used to pass a pointer to the goroutine function. The code in the question uses the method's receiver argument. The code in the FAQ uses a closure.
Upvotes: 17
Reputation: 166925
Go Frequently Asked Questions (FAQ)
What happens with closures running as goroutines?
Some confusion may arise when using closures with concurrency. Consider the following program:
func main() { done := make(chan bool) values := []string{"a", "b", "c"} for _, v := range values { go func() { fmt.Println(v) done <- true }() } // wait for all goroutines to complete before exiting for _ = range values { <-done } }
One might mistakenly expect to see a, b, c as the output. What you'll probably see instead is c, c, c. This is because each iteration of the loop uses the same instance of the variable v, so each closure shares that single variable. When the closure runs, it prints the value of v at the time fmt.Println is executed, but v may have been modified since the goroutine was launched. To help detect this and other problems before they happen, run go vet.
To bind the current value of v to each closure as it is launched, one must modify the inner loop to create a new variable each iteration. One way is to pass the variable as an argument to the closure:
for _, v := range values { go func(u string) { fmt.Println(u) done <- true }(v) }
In this example, the value of v is passed as an argument to the anonymous function. That value is then accessible inside the function as the variable u.
Even easier is just to create a new variable, using a declaration style that may seem odd but works fine in Go:
for _, v := range values { v := v // create a new 'v'. go func() { fmt.Println(v) done <- true }() }
Just create a new variable for the closure using a declaration style that may seem odd but works fine in Go. Add task := task
. For example,
package main
import (
"fmt"
"time"
)
type Task struct {
name string
data int32
}
func (this *Task) PrintData() {
fmt.Println(this.name, ":", this.data)
}
func main() {
tasks := []Task{{"hello", 1}, {"world", 2}}
for _, task := range tasks {
task := task
go task.PrintData()
}
time.Sleep(time.Second * 5000)
}
Output:
hello : 1
world : 2
Upvotes: 3