yeeco/gyee: p2p/peer/peer.go; 5 LoC

Found a possible issue in [yeeco/gyee](https://www.github.com/yeeco/gyee) at [p2p/peer/peer.go](https://github.com/yeeco/gyee/blob/05aca43e839014daa2d772ced8cdfa9a1f4b196d/p2p/peer/peer.go#L634-L638)

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.

> function call at line 636 may store a reference to snid

[Click here to see the code in its original context.](https://github.com/yeeco/gyee/blob/05aca43e839014daa2d772ced8cdfa9a1f4b196d/p2p/peer/peer.go#L634-L638)

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

```go
for snid := range appended {
schMsg := sch.SchMessage{}
peMgr.sdl.SchMakeMessage(&schMsg, peMgr.ptnMe, peMgr.ptnMe, sch.EvPeOutboundReq, &snid)
peMgr.sdl.SchSendMessage(&schMsg)
}

```

Click here to show extra information the analyzer produced.

```
The following dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
no paths found; call may have ended in third-party code; stay tuned for diagnostics
```

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: 05aca43e839014daa2d772ced8cdfa9a1f4b196d