github-vet / github-vet/rangeloop-pointer-findings
mgechev/revive: testdata/range-val-address.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [mgechev/revive](https://www.github.com/mgechev/revive) at [testdata/range-val-address.go](https://github.com/mgechev/revive/blob/80884d48fd59e0c4d2a574212cd27356d577d4c0/testdata/range-val-address.go#L25-L28)
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 value is reassigned at line 26
[Click here to see the code in its original context.](https://github.com/mgechev/revive/blob/80884d48fd59e0c4d2a574212cd27356d577d4c0/testdata/range-val-address.go#L25-L28)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for _, value := range mySlice {
a := &value // MATCH /suspicious assignment of 'value'. range-loop variables always have the same address/
m["address"] = a
}
```
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: 80884d48fd59e0c4d2a574212cd27356d577d4c0
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.