weaveworks/weave: nameserver/entry.go; 5 LoC

Found a possible issue in [weaveworks/weave](https://www.github.com/weaveworks/weave) at [nameserver/entry.go](https://github.com/weaveworks/weave/blob/d81e908d1a4ab455ad5c3ee2c2eb3feba5ccdbb7/nameserver/entry.go#L251-L255)

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/weaveworks/weave/blob/d81e908d1a4ab455ad5c3ee2c2eb3feba5ccdbb7/nameserver/entry.go#L251-L255)

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

```go
for _, e := range es {
if f(&e) {
return &e, nil
}
}

```

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 {f 1} 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: d81e908d1a4ab455ad5c3ee2c2eb3feba5ccdbb7

Review nameserver/entry.go around lines 251-255 and the linked commit context to determine whether returning a pointer to the range variable is a bug, mitigated, or desirable behavior. Record the conclusion using the issue's requested reaction classification.

Written by the indexing model from the issue text.