Wouterbeets/snake: game.go; 7 LoC

Found a possible issue in [Wouterbeets/snake](https://www.github.com/Wouterbeets/snake) at [game.go](https://github.com/Wouterbeets/snake/blob/aca83a5095dcf51742ee9553ea4ec2dc2d4db6d2/game.go#L83-L89)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> range-loop variable i used in defer or goroutine at line 87

[Click here to see the code in its original context.](https://github.com/Wouterbeets/snake/blob/aca83a5095dcf51742ee9553ea4ec2dc2d4db6d2/game.go#L83-L89)

Click here to show the 7 line(s) of Go which triggered the analyzer.

```go
for i := range g.Players {
wg.Add(1)
go func() {
defer wg.Done()
cmove <- g.Players[i].Play(g)
}()
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: aca83a5095dcf51742ee9553ea4ec2dc2d4db6d2

Read game.go at lines 83-89 and inspect how the range-loop index is used inside the goroutine. Compare the analyzer finding with the surrounding game logic, then classify it as Bug, Mitigated, or Desirable Behavior using the linked project guidance and leave the corresponding reaction.

Written by the indexing model from the issue text.