github-vet / github-vet/rangeloop-pointer-findings
mibk/hawk: compiler/internal/hawkc/stmt.go; 14 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [mibk/hawk](https://www.github.com/mibk/hawk) at [compiler/internal/hawkc/stmt.go](https://github.com/mibk/hawk/blob/f6948cc84d53e96bc2ee700e5e4909a013c955cb/compiler/internal/hawkc/stmt.go#L176-L189)
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.
> function call at line 178 may store a reference to k
[Click here to see the code in its original context.](https://github.com/mibk/hawk/blob/f6948cc84d53e96bc2ee700e5e4909a013c955cb/compiler/internal/hawkc/stmt.go#L176-L189)
Click here to show the 14 line(s) of Go which triggered the analyzer.
```go
for _, k := range a.Keys() {
if fs.Key != nil {
fs.Key.scope.Put(fs.Key.Name, &k)
}
if fs.Val != nil {
fs.Val.scope.Put(fs.Val.Name, a.Get(&k))
}
switch fs.Body.Exec(w) {
case StatusBreak:
return StatusNone
case StatusReturn:
return StatusReturn
}
}
```
Click here to show extra information the analyzer produced.
```
The following dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
no paths found; call may have ended in third-party code; stay tuned for diagnostics
```
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: f6948cc84d53e96bc2ee700e5e4909a013c955cb
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.