Sam-Lane/hue: pkg/commands/lights.go; 3 LoC

Found a possible issue in [Sam-Lane/hue](https://www.github.com/Sam-Lane/hue) at [pkg/commands/lights.go](https://github.com/Sam-Lane/hue/blob/c967b0c4600fd862a52b3f558648793c5bb467a6/pkg/commands/lights.go#L40-L42)

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/Sam-Lane/hue/blob/c967b0c4600fd862a52b3f558648793c5bb467a6/pkg/commands/lights.go#L40-L42)

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

```go
for _, l := range lights {
printLight(c, &l)
}

```

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 {printLight 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: c967b0c4600fd862a52b3f558648793c5bb467a6

Inspect pkg/commands/lights.go around the shown loop and the printLight entry point, then review the analyzer guidance linked in the issue. Decide whether this range-variable pointer use is a Bug, Mitigated, or Desirable Behavior, and leave the corresponding reaction; completion is the classification reaction.

Written by the indexing model from the issue text.