github-vet / github-vet/rangeloop-pointer-findings
Appliscale/perun: stack/updatingstack.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [Appliscale/perun](https://www.github.com/Appliscale/perun) at [stack/updatingstack.go](https://github.com/Appliscale/perun/blob/a4d1c73c9f6867fa755ee531f61374a7200e185a/stack/updatingstack.go#L72-L74)
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 capability is reassigned at line 73
[Click here to see the code in its original context.](https://github.com/Appliscale/perun/blob/a4d1c73c9f6867fa755ee531f61374a7200e185a/stack/updatingstack.go#L72-L74)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for i, capability := range rawCapabilities {
capabilities[i] = &capability
}
```
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: a4d1c73c9f6867fa755ee531f61374a7200e185a
Contributor guide
No contributing guide indexed for this repository
Research direction
Open stack/updatingstack.go at lines 72-74 and inspect the surrounding use of rawCapabilities and capabilities. Compare the analyzer finding with the linked classification guidance; done means leaving the appropriate reaction on the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100