github-vet / github-vet/rangeloop-pointer-findings
nileshsimaria/tygs: range1/main.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [nileshsimaria/tygs](https://www.github.com/nileshsimaria/tygs) at [range1/main.go](https://github.com/nileshsimaria/tygs/blob/33eccd35269a74fc1f8319e561f79d3ece397917/range1/main.go#L9-L11)
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.
> reference to v is reassigned at line 10
[Click here to see the code in its original context.](https://github.com/nileshsimaria/tygs/blob/33eccd35269a74fc1f8319e561f79d3ece397917/range1/main.go#L9-L11)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for i, v := range a {
b[i] = &v
}
```
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: 33eccd35269a74fc1f8319e561f79d3ece397917
Contributor guide
No contributing guide indexed for this repository
Research direction
Open range1/main.go at lines 9–11 and inspect how the range variable is referenced inside the loop. Review the linked analyzer finding and the repository’s classification guidance, then leave the appropriate reaction to mark the instance as Bug, Mitigated, or Desirable Behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100