xiegeo/thuder: collections.go; 3 LoC

Found a possible issue in [xiegeo/thuder](https://www.github.com/xiegeo/thuder) at [collections.go](https://github.com/xiegeo/thuder/blob/ac019673806858398d2a9d52420b4c9515fa498f/collections.go#L38-L40)

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/xiegeo/thuder/blob/ac019673806858398d2a9d52420b4c9515fa498f/collections.go#L38-L40)

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

```go
for k, v := range c.nodes {
f("%s: %s\n", k, &v)
}

```

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 {f 3} 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: ac019673806858398d2a9d52420b4c9515fa498f

Inspect collections.go at lines 38-40 in the linked xiegeo/thuder commit, then compare the range-loop pointer usage with the analyzer's output. Classify the finding 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.