github-vet / github-vet/rangeloop-pointer-findings
sbotman/go-training: 06-testing/example1/example1.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [sbotman/go-training](https://www.github.com/sbotman/go-training) at [06-testing/example1/example1.go](https://github.com/sbotman/go-training/blob/0c1c429e241e09e34e90b85d2c4944c6a095c766/06-testing/example1/example1.go#L48-L50)
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/sbotman/go-training/blob/0c1c429e241e09e34e90b85d2c4944c6a095c766/06-testing/example1/example1.go#L48-L50)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, station := range stations {
buoy.Print(&station)
}
```
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 {Print 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: 0c1c429e241e09e34e90b85d2c4944c6a095c766
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.