github-vet / github-vet/rangeloop-pointer-findings
paulnguyen/cmpe281: golabs/golang/effective/src/app/23.concurrency3.go; 7 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [paulnguyen/cmpe281](https://www.github.com/paulnguyen/cmpe281) at [golabs/golang/effective/src/app/23.concurrency3.go](https://github.com/paulnguyen/cmpe281/blob/aa390f6522a109fed7960e8eeaf815e3c031aa13/golabs/golang/effective/src/app/23.concurrency3.go#L67-L73)
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 req used in defer or goroutine at line 70
[Click here to see the code in its original context.](https://github.com/paulnguyen/cmpe281/blob/aa390f6522a109fed7960e8eeaf815e3c031aa13/golabs/golang/effective/src/app/23.concurrency3.go#L67-L73)
Click here to show the 7 line(s) of Go which triggered the analyzer.
```go
for req := range queue {
sem <- 1
go func() {
process(req) // Buggy; see explanation below.
<-sem
}()
}
```
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: aa390f6522a109fed7960e8eeaf815e3c031aa13
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.