github-vet / github-vet/rangeloop-pointer-findings
jollheef/tin_foil_hat: scoreboard/api.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [jollheef/tin_foil_hat](https://www.github.com/jollheef/tin_foil_hat) at [scoreboard/api.go](https://github.com/jollheef/tin_foil_hat/blob/0c6d56449ddaeb1d55ad4fe3f5f7294c069ef489/scoreboard/api.go#L50-L52)
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.
> range-loop variable l used in defer or goroutine at line 51
[Click here to see the code in its original context.](https://github.com/jollheef/tin_foil_hat/blob/0c6d56449ddaeb1d55ad4fe3f5f7294c069ef489/scoreboard/api.go#L50-L52)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for l := range b.listeners {
go func() { l <- attack }()
}
```
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: 0c6d56449ddaeb1d55ad4fe3f5f7294c069ef489
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the reported range-loop closure in scoreboard/api.go at lines 50-52 and the linked commit context. Compare the analyzer finding with the intended behavior, then leave the requested Bug, Mitigated, or Desirable Behavior reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100