github-vet / github-vet/rangeloop-pointer-findings
rgeorgiev583/fmi-golang: 2/ordered-log-drainer.go; 12 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [rgeorgiev583/fmi-golang](https://www.github.com/rgeorgiev583/fmi-golang) at [2/ordered-log-drainer.go](https://github.com/rgeorgiev583/fmi-golang/blob/e8b5adea027d453e106736f7ae6ebf257279a62b/2/ordered-log-drainer.go#L26-L37)
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 log used in defer or goroutine at line 30
[Click here to see the code in its original context.](https://github.com/rgeorgiev583/fmi-golang/blob/e8b5adea027d453e106736f7ae6ebf257279a62b/2/ordered-log-drainer.go#L26-L37)
Click here to show the 12 line(s) of Go which triggered the analyzer.
```go
for log := range logs {
go func(i int) {
//<-syncer
for logEntry := range log {
mergedLogs <- fmt.Sprintf("%d\t%s", i, logEntry)
}
//syncer <- struct{}{}
}(i)
i++
}
```
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: e8b5adea027d453e106736f7ae6ebf257279a62b
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.