superLimitBreak/channelMq: group.go; 10 LoC

Found a possible issue in [superLimitBreak/channelMq](https://www.github.com/superLimitBreak/channelMq) at [group.go](https://github.com/superLimitBreak/channelMq/blob/2c8e20854f2cc2e03535ea453dae93be597dd5af/group.go#L31-L40)

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 ch used in defer or goroutine at line 34

[Click here to see the code in its original context.](https://github.com/superLimitBreak/channelMq/blob/2c8e20854f2cc2e03535ea453dae93be597dd5af/group.go#L31-L40)

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

```go
for ch, _ := range g.members {
go func() {
select {
case ch <- msg:
return
case <-time.After(200 * time.Millisecond):
return
}
}()
}

```

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: 2c8e20854f2cc2e03535ea453dae93be597dd5af

Read group.go at lines 31-40 and inspect how the goroutine uses the range variable ch. Check the analyzer’s range-loop capture guidance, then verify the warning is addressed without changing the intended message-delivery behavior.

Written by the indexing model from the issue text.