pulcy/robin: deps/github.com/coreos/etcd/storage/watchable_store.go; 5 LoC

Found a possible issue in [pulcy/robin](https://www.github.com/pulcy/robin) at [deps/github.com/coreos/etcd/storage/watchable_store.go](https://github.com/pulcy/robin/blob/93d971c7dff93e8ec0172633ab5e7118e900af74/deps/github.com/coreos/etcd/storage/watchable_store.go#L154-L158)

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.

> reference to change was used in a composite literal at line 157

[Click here to see the code in its original context.](https://github.com/pulcy/robin/blob/93d971c7dff93e8ec0172633ab5e7118e900af74/deps/github.com/coreos/etcd/storage/watchable_store.go#L154-L158)

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

```go
for i, change := range changes {
evs[i] = storagepb.Event{
Type: storagepb.DELETE,
Kv: &change}
}

```

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: 93d971c7dff93e8ec0172633ab5e7118e900af74

Open deps/github.com/coreos/etcd/storage/watchable_store.go at lines 154-158 for commit 93d971c7dff93e8ec0172633ab5e7118e900af74 and review the reported range-loop reference. Read the repository's classification guidance, then determine whether the finding is a bug, mitigated, or desirable behavior and record that classification with the requested reaction.

Written by the indexing model from the issue text.