pcwilcox/toy-dynamo: gossip.go; 5 LoC

Found a possible issue in [pcwilcox/toy-dynamo](https://www.github.com/pcwilcox/toy-dynamo) at [gossip.go](https://github.com/pcwilcox/toy-dynamo/blob/e1addcf2df05330f067249aea0d44cfdeb27a851/gossip.go#L126-L130)

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.

>

[Click here to see the code in its original context.](https://github.com/pcwilcox/toy-dynamo/blob/e1addcf2df05330f067249aea0d44cfdeb27a851/gossip.go#L126-L130)

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

```go
for key, aliceEntry := range inglob.Keys {
if g.ConflictResolution(key, &aliceEntry) {
g.kvs.OverwriteEntry(key, &aliceEntry)
}
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {ConflictResolution 2} was not found in the callgraph; reference was passed directly to third-party code
```

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

Start with gossip.go lines 126-130, then trace ConflictResolution and kvs.OverwriteEntry to understand whether the range-loop pointer reaches code that can retain or modify it. Decide whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior, and leave the corresponding reaction.

Written by the indexing model from the issue text.