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.
function call at line 63 may store a reference to v
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, v := range vs {
testy(&v)
}
```
Click here to show extra information the analyzer produced.
```
The following graphviz dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
digraph G {
"(testy, 1)" -> {}
}
No path was found through the callgraph that could lead to a function which passes a pointer 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 for more information.
Found a possible issue in kalexmills/bad-go at main.go
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.
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go for _, v := range vs { testy(&v) } ```Click here to show extra information the analyzer produced.
``` The following graphviz dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument: digraph G { "(testy, 1)" -> {} } No path was found through the callgraph that could lead to a function which passes a pointer 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 for more information.
commit ID: d69ce462fe9c31f699a49a072751d377d823599d