github-vet / github-vet/rangeloop-pointer-findings
jelmersnoeck/experiment: experiment.go; 8 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [jelmersnoeck/experiment](https://www.github.com/jelmersnoeck/experiment) at [experiment.go](https://github.com/jelmersnoeck/experiment/blob/9f66c7787af73bf865d08d0f2d7e779cd8689ce9/experiment.go#L182-L189)
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 k used in defer or goroutine at line 184
[Click here to see the code in its original context.](https://github.com/jelmersnoeck/experiment/blob/9f66c7787af73bf865d08d0f2d7e779cd8689ce9/experiment.go#L182-L189)
Click here to show the 8 line(s) of Go which triggered the analyzer.
```go
for k, v := range e.candidates {
go func(name string, fnc CandidateFunc) {
runCandidate(k, v, obsChan)
}(k, v)
obs := <-obsChan
e.observations[obs.Name] = obs
}
```
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: 9f66c7787af73bf865d08d0f2d7e779cd8689ce9
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.