github-vet / github-vet/rangeloop-pointer-findings
elauffenburger/oar: core/core.go; 19 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [elauffenburger/oar](https://www.github.com/elauffenburger/oar) at [core/core.go](https://github.com/elauffenburger/oar/blob/331ffc01278dd9c890959ef699f931278b8ee756/core/core.go#L119-L137)
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 134 may store a reference to t
[Click here to see the code in its original context.](https://github.com/elauffenburger/oar/blob/331ffc01278dd9c890959ef699f931278b8ee756/core/core.go#L119-L137)
Click here to show the 19 line(s) of Go which triggered the analyzer.
```go
for typename, t := range config.Types {
if _, exists := types[typename]; exists {
continue
}
loadername := t.LoaderArgs.Name
factory, ok := (*typeLoaderFactoryCtx)[loadername]
if !ok {
// todo handle unknown loader
continue
}
// create a loader for this type
loader := factory()
loader.Load(&t)
types[typename] = loader
}
```
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: 331ffc01278dd9c890959ef699f931278b8ee756
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.