nilslice/protolock: parse.go; 19 LoC

Found a possible issue in [nilslice/protolock](https://www.github.com/nilslice/protolock) at [parse.go](https://github.com/nilslice/protolock/blob/83d9d31557c3806e166c6930a119216f8911459d/parse.go#L474-L492)

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 rule used in defer or goroutine at line 478

[Click here to see the code in its original context.](https://github.com/nilslice/protolock/blob/83d9d31557c3806e166c6930a119216f8911459d/parse.go#L474-L492)

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

```go
for _, rule := range Rules {
wg.Add(1)
go func() {
if debug {
beginRuleDebug(rule.Name)
}
_warnings, _ := rule.Func(current, update)
for i := range _warnings {
_warnings[i].RuleName = rule.Name
}
if debug {
concludeRuleDebug(rule.Name, _warnings)
}

warnings = append(warnings, _warnings...)
wg.Done()
}()
wg.Wait()
}

```

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: 83d9d31557c3806e166c6930a119216f8911459d

Read parse.go around lines 474-492 and inspect the surrounding range loop, goroutine, and synchronization. Compare the analyzer's range-loop capture warning with the code's behavior, then classify the finding as Bug, Mitigated, or Desirable Behavior by leaving the corresponding reaction on the issue.

Written by the indexing model from the issue text.