github-vet / github-vet/rangeloop-pointer-findings
anandkunal/sqsdrain: sqsdrain.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [anandkunal/sqsdrain](https://www.github.com/anandkunal/sqsdrain) at [sqsdrain.go](https://github.com/anandkunal/sqsdrain/blob/b8f7e3c9e6a18e25125553ab96528526b0f8befe/sqsdrain.go#L29-L31)
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 which takes a reference to m at line 30 may start a goroutine
[Click here to see the code in its original context.](https://github.com/anandkunal/sqsdrain/blob/b8f7e3c9e6a18e25125553ab96528526b0f8befe/sqsdrain.go#L29-L31)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, m := range response.Messages {
queue.DeleteMessage(&m)
}
```
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: b8f7e3c9e6a18e25125553ab96528526b0f8befe
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.