umarquez/0ms2-game: background.go; 14 LoC

Found a possible issue in [umarquez/0ms2-game](https://www.github.com/umarquez/0ms2-game) at [background.go](https://github.com/umarquez/0ms2-game/blob/4c47844020ad7a115642341bfdf1993d8e6dfa3b/background.go#L58-L71)

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.

>

[Click here to see the code in its original context.](https://github.com/umarquez/0ms2-game/blob/4c47844020ad7a115642341bfdf1993d8e6dfa3b/background.go#L58-L71)

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

```go
for k := range tilesCollection {
pos := copyVector(bg.player.currentTile.GetPosition().Min)
pos.Add(&k).Add(&vec2.T{windowWidth / 2, windowHeight / 2})

if k == positionCurrent {
pos = copyVector(*bg.player.position)
pos.Scale(j0hnScale)
}

if tile.GetPosition().ContainsPoint(&pos) {
tilesCollection[k] = tile
break
}
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {Add 1} was not found in the callgraph; reference was passed directly to third-party code
```

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: 4c47844020ad7a115642341bfdf1993d8e6dfa3b

Inspect background.go at lines 58-71 in commit 4c47844020ad7a115642341bfdf1993d8e6dfa3b, starting with the range loop over tilesCollection and its pointer-related analyzer context. Compare the loop-variable references with the analyzer guidance, then classify the finding as Bug, Mitigated, or Desirable Behavior using the linked project descriptions.

Written by the indexing model from the issue text.