github-vet / github-vet/rangeloop-pointer-findings
hoop33/limo: cmd/prune.go; 6 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [hoop33/limo](https://www.github.com/hoop33/limo) at [cmd/prune.go](https://github.com/hoop33/limo/blob/4ff783641324ea33f85f176b970784a0112c5956/cmd/prune.go#L36-L41)
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 star was used in a composite literal at line 37
[Click here to see the code in its original context.](https://github.com/hoop33/limo/blob/4ff783641324ea33f85f176b970784a0112c5956/cmd/prune.go#L36-L41)
Click here to show the 6 line(s) of Go which triggered the analyzer.
```go
for _, star := range prunable {
output.StarLine(&star)
if del {
fatalOnError(star.Delete(db))
}
}
```
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: 4ff783641324ea33f85f176b970784a0112c5956
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with cmd/prune.go at lines 36-41 and review the linked analyzer report for the range-loop reference. Use the rangeclosure-findings classification guidance to determine whether this instance is a bug, mitigated, or desirable behavior; completion means recording the appropriate classification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100