rgeorgiev583/fmi-golang: 2/solution.go; 9 LoC

Found a possible issue in [rgeorgiev583/fmi-golang](https://www.github.com/rgeorgiev583/fmi-golang) at [2/solution.go](https://github.com/rgeorgiev583/fmi-golang/blob/e8b5adea027d453e106736f7ae6ebf257279a62b/2/solution.go#L13-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 log used in defer or goroutine at line 15

[Click here to see the code in its original context.](https://github.com/rgeorgiev583/fmi-golang/blob/e8b5adea027d453e106736f7ae6ebf257279a62b/2/solution.go#L13-L21)

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

```go
for log := range logs {
go func(i int) {
for logEntry := range log {
mergedLogs <- fmt.Sprintf("%d\t%s", i, logEntry)
}
}(i)

i++
}

```

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

Inspect 2/solution.go at the linked lines and read the repository's classification guidance for range-loop findings. Done means leaving the appropriate reaction to classify the reported analyzer finding as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.