xeger/mongoose: gen/renderer.go; 6 LoC

Found a possible issue in [xeger/mongoose](https://www.github.com/xeger/mongoose) at [gen/renderer.go](https://github.com/xeger/mongoose/blob/49215995687c5323c46ce9a2e0c145f154ff0773/gen/renderer.go#L85-L90)

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 intf was used in a composite literal at line 86

[Click here to see the code in its original context.](https://github.com/xeger/mongoose/blob/49215995687c5323c46ce9a2e0c145f154ff0773/gen/renderer.go#L85-L90)

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

```go
for _, intf := range intfs {
err := tr.Item.Execute(&out, itemContext{Resolver: tr.Resolver, Package: pkg, Interface: &intf})
if err != nil {
return "", err
}
}

```

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: 49215995687c5323c46ce9a2e0c145f154ff0773

Start by reading gen/renderer.go lines 85-90 at commit 49215995687c5323c46ce9a2e0c145f154ff0773 and inspect the surrounding range loop. Decide whether the analyzer finding is Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction.

Written by the indexing model from the issue text.