github-vet / github-vet/rangeloop-pointer-findings
mikedewar/st-core-old: thinking/promises/demo.go; 10 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [mikedewar/st-core-old](https://www.github.com/mikedewar/st-core-old) at [thinking/promises/demo.go](https://github.com/mikedewar/st-core-old/blob/2f44752e5bcde284931d956d9e214ddda80d487d/thinking/promises/demo.go#L39-L48)
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 inPromise used in defer or goroutine at line 45
[Click here to see the code in its original context.](https://github.com/mikedewar/st-core-old/blob/2f44752e5bcde284931d956d9e214ddda80d487d/thinking/promises/demo.go#L39-L48)
Click here to show the 10 line(s) of Go which triggered the analyzer.
```go
for inPromise := range in {
outPromise := make(Promise)
out <- outPromise
go func() {
m := <-inPromise
outPromise <- b.kernel(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: 2f44752e5bcde284931d956d9e214ddda80d487d
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.