mami-project/three-bits-suffice: quic/pinq/connection.go; 5 LoC

Found a possible issue in [mami-project/three-bits-suffice](https://www.github.com/mami-project/three-bits-suffice) at [quic/pinq/connection.go](https://github.com/mami-project/three-bits-suffice/blob/829d1134b493a7938bc0853bac732c437e8be497/quic/pinq/connection.go#L1368-L1372)

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/mami-project/three-bits-suffice/blob/829d1134b493a7938bc0853bac732c437e8be497/quic/pinq/connection.go#L1368-L1372)

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

```go
for _, t := range in {
if f(&t) {
out = append(out, t)
}
}

```

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 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: 829d1134b493a7938bc0853bac732c437e8be497

Review quic/pinq/connection.go at lines 1368-1372 for commit 829d1134b493a7938bc0853bac732c437e8be497, along with the linked analyzer context. Decide whether the range-variable pointer use is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction.

Written by the indexing model from the issue text.