go-services/source: source.go; 5 LoC

Found a possible issue in [go-services/source](https://www.github.com/go-services/source) at [source.go](https://github.com/go-services/source/blob/8fa8c1041cb712ed6c67e878cf45a4476ad5f75a/source.go#L229-L233)

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/go-services/source/blob/8fa8c1041cb712ed6c67e878cf45a4476ad5f75a/source.go#L229-L233)

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

```go
for _, m := range ifc.Methods() {
if m.Name() == method {
return s.comment(&m, comment)
}
}

```

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 {comment 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: 8fa8c1041cb712ed6c67e878cf45a4476ad5f75a

Start with source.go lines 229-233 and inspect how the range variable m is passed to s.comment. Use the analyzer details and the linked code context to determine whether this is a bug, mitigated behavior, or desirable behavior, then classify the finding with the corresponding reaction.

Written by the indexing model from the issue text.