github-vet / github-vet/rangeloop-pointer-findings
denistsoi/dt-go: 12-goroutine/main.go; 7 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [denistsoi/dt-go](https://www.github.com/denistsoi/dt-go) at [12-goroutine/main.go](https://github.com/denistsoi/dt-go/blob/bb3b90d6753d60023a03b807745abab2c4bced70/12-goroutine/main.go#L24-L30)
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 27
[Click here to see the code in its original context.](https://github.com/denistsoi/dt-go/blob/bb3b90d6753d60023a03b807745abab2c4bced70/12-goroutine/main.go#L24-L30)
Click here to show the 7 line(s) of Go which triggered the analyzer.
```go
for l := range c {
go func(link string) {
time.Sleep(time.Second)
checkLink(l, c)
}(l)
}
```
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: bb3b90d6753d60023a03b807745abab2c4bced70
Contributor guide
No contributing guide indexed for this repository
Research direction
Read 12-goroutine/main.go at lines 24-30 and examine how the goroutine uses the range variable. Decide whether the analyzer finding is a real bug, mitigated, or desirable behavior, then leave the corresponding reaction requested by the issue. No test or patch is specified.
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