github-vet / github-vet/rangeloop-pointer-findings
zusux/go_ddns: 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 [zusux/go_ddns](https://www.github.com/zusux/go_ddns) at [main.go](https://github.com/zusux/go_ddns/blob/41abf172f6dae85f5a79bfc01a0202c65510786f/main.go#L108-L114)
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 t used in defer or goroutine at line 110
[Click here to see the code in its original context.](https://github.com/zusux/go_ddns/blob/41abf172f6dae85f5a79bfc01a0202c65510786f/main.go#L108-L114)
Click here to show the 7 line(s) of Go which triggered the analyzer.
```go
for t := range ticker.C {
go func() {
fmt.Println(t)
Run()
fmt.Println("")
}()
}
```
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: 41abf172f6dae85f5a79bfc01a0202c65510786f
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect main.go lines 108-114 and the shown goroutine to understand how the range variable t is used. Decide whether the analyzer finding represents a Bug, Mitigated case, or Desirable Behavior, then leave the corresponding reaction on the issue; completion is the classification reaction.
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
- 45/100