logd-team/logd: fileOutputer.go; 3 LoC

Found a possible issue in [logd-team/logd](https://www.github.com/logd-team/logd) at [fileOutputer.go](https://github.com/logd-team/logd/blob/4d122b38ea263dff86790ecc356369c40178b6f0/fileOutputer.go#L69-L71)

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/logd-team/logd/blob/4d122b38ea263dff86790ecc356369c40178b6f0/fileOutputer.go#L69-L71)

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

```go
for b := range f.buffer {
f.extract(&b)
}

```

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 {extract 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: 4d122b38ea263dff86790ecc356369c40178b6f0

Inspect fileOutputer.go at lines 69-71 and read the surrounding buffer-processing code. Review the analyzer output and the linked code context to determine whether the range-loop pointer finding is a real bug, mitigated, or desirable behavior; done means classifying the finding with the appropriate reaction.

Written by the indexing model from the issue text.