github-vet / github-vet/rangeloop-pointer-findings
octaviogb/Poligrafo: main.go; 6 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [octaviogb/Poligrafo](https://www.github.com/octaviogb/Poligrafo) at [main.go](https://github.com/octaviogb/Poligrafo/blob/cc760076075cd33ac2708ae6f35add5f9e8b6886/main.go#L163-L168)
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 transaction is reassigned at line 165
[Click here to see the code in its original context.](https://github.com/octaviogb/Poligrafo/blob/cc760076075cd33ac2708ae6f35add5f9e8b6886/main.go#L163-L168)
Click here to show the 6 line(s) of Go which triggered the analyzer.
```go
for _, transaction := range transactions {
if transaction.Duplicated {
duplicated = &transaction
continue
}
}
```
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: cc760076075cd33ac2708ae6f35add5f9e8b6886
Contributor guide
No contributing guide indexed for this repository
Research direction
Open main.go at lines 163-168 in the linked Poligrafo commit and read the surrounding loop and uses of duplicated. Check whether the reported reassignment affects the resulting behavior, then leave the reaction that matches the finding: Bug, Mitigated, or Desirable Behavior.
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