stels-cs/vk-api-tools: BotLongPoll.go; 3 LoC

Found a possible issue in [stels-cs/vk-api-tools](https://www.github.com/stels-cs/vk-api-tools) at [BotLongPoll.go](https://github.com/stels-cs/vk-api-tools/blob/d6fc8ec269d3921dbb37bad38860bb107bfebbdd/BotLongPoll.go#L209-L211)

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/stels-cs/vk-api-tools/blob/d6fc8ec269d3921dbb37bad38860bb107bfebbdd/BotLongPoll.go#L209-L211)

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

```go
for _, upd := range updates {
s.listener(&upd)
}

```

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 {listener 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: d6fc8ec269d3921dbb37bad38860bb107bfebbdd

Start with BotLongPoll.go at lines 209-211 and read the surrounding update loop and listener entry point. Determine whether passing the address of upd can expose an unintended range-loop reference, then check the listener contract and existing repository behavior. Done means classifying the analyzer finding as a bug, mitigated, or desirable behavior and documenting the conclusion.

Written by the indexing model from the issue text.