aix3/upgraded-octo-enigma: funcref/funcref.go; 5 LoC

Found a possible issue in [aix3/upgraded-octo-enigma](https://www.github.com/aix3/upgraded-octo-enigma) at [funcref/funcref.go](https://github.com/aix3/upgraded-octo-enigma/blob/e3bb6a22d74980118458a7acf6b2ba609eca1f7f/funcref/funcref.go#L17-L21)

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.

> range-loop variable f used in defer or goroutine at line 19

[Click here to see the code in its original context.](https://github.com/aix3/upgraded-octo-enigma/blob/e3bb6a22d74980118458a7acf6b2ba609eca1f7f/funcref/funcref.go#L17-L21)

Click here to show the 5 line(s) of Go which triggered the analyzer.

```go
for _, f := range funcs {
go func(ff func()) {
f()
}(f)
}

```

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: e3bb6a22d74980118458a7acf6b2ba609eca1f7f

Open funcref/funcref.go at lines 17–21 and inspect the goroutine call in the linked commit context. Determine whether the reported range-loop usage is a bug, mitigated, or desirable behavior, then leave the corresponding reaction on the issue.

Written by the indexing model from the issue text.