Jille/rufs: filescanner/filescanner.go; 8 LoC

Found a possible issue in [Jille/rufs](https://www.github.com/Jille/rufs) at [filescanner/filescanner.go](https://github.com/Jille/rufs/blob/d4f9316126bda9ee35bb24ea6e1fd8d58423febb/filescanner/filescanner.go#L200-L207)

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/Jille/rufs/blob/d4f9316126bda9ee35bb24ea6e1fd8d58423febb/filescanner/filescanner.go#L200-L207)

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

```go
for fn, fi := range cpy {
select {
case <-ctx.Done():
return
default:
}
callback(ctx, fn, &fi, 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 {callback 4} 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: d4f9316126bda9ee35bb24ea6e1fd8d58423febb

Read filescanner/filescanner.go at lines 200-207 and the linked analyzer context first. Determine whether the range-loop pointer finding is a bug, mitigated, or desirable behavior, then record the classification with the matching reaction.

Written by the indexing model from the issue text.