LilyFaFa/Algorithm-in-deep-night: golang/channel/channel.go; 6 LoC

Found a possible issue in [LilyFaFa/Algorithm-in-deep-night](https://www.github.com/LilyFaFa/Algorithm-in-deep-night) at [golang/channel/channel.go](https://github.com/LilyFaFa/Algorithm-in-deep-night/blob/e7444db81deb096b269315cdafb9c8484460cde7/golang/channel/channel.go#L69-L74)

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 i used in defer or goroutine at line 72

[Click here to see the code in its original context.](https://github.com/LilyFaFa/Algorithm-in-deep-night/blob/e7444db81deb096b269315cdafb9c8484460cde7/golang/channel/channel.go#L69-L74)

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

```go
for _, i := range mem {
fmt.Println(i)
go func() {
ch <- 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: e7444db81deb096b269315cdafb9c8484460cde7

Read golang/channel/channel.go lines 69-74 and the linked commit context; inspect how the goroutine uses the range variable i. Compare the analyzer finding with the repository's intended channel behavior, then leave the requested reaction classification on the issue.

Written by the indexing model from the issue text.