intelligide/gbuilder: lib/gbuilder/builder.go; 6 LoC

Found a possible issue in [intelligide/gbuilder](https://www.github.com/intelligide/gbuilder) at [lib/gbuilder/builder.go](https://github.com/intelligide/gbuilder/blob/44a1084e9508e294cd993855fd4e5385eb89fd07/lib/gbuilder/builder.go#L130-L135)

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 name used in defer or goroutine at line 133

[Click here to see the code in its original context.](https://github.com/intelligide/gbuilder/blob/44a1084e9508e294cd993855fd4e5385eb89fd07/lib/gbuilder/builder.go#L130-L135)

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

```go
for _, name := range targetNames {
go func() {
defer wg.Done()
this.Install(name, tags)
}()
}

```

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: 44a1084e9508e294cd993855fd4e5385eb89fd07

Start by reading lib/gbuilder/builder.go around lines 130-135 and the analyzer message about the range-loop variable used in a goroutine. Check the surrounding code and the linked commit context to decide whether this is a real bug, mitigated, or desirable behavior. Done means leaving the corresponding classification reaction on the issue.

Written by the indexing model from the issue text.