mickelsonm/go-helpers: rabbitmq/consumer.go; 4 LoC

Found a possible issue in [mickelsonm/go-helpers](https://www.github.com/mickelsonm/go-helpers) at [rabbitmq/consumer.go](https://github.com/mickelsonm/go-helpers/blob/5176009d7a07c9265a228c9ce49a4ac325bdb971/rabbitmq/consumer.go#L35-L38)

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/mickelsonm/go-helpers/blob/5176009d7a07c9265a228c9ce49a4ac325bdb971/rabbitmq/consumer.go#L35-L38)

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

```go
for msg := range c.incomingMessages {
handler.HandleMessage(&msg)
msg.Ack(false)
}

```

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 {HandleMessage 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: 5176009d7a07c9265a228c9ce49a4ac325bdb971

Start with rabbitmq/consumer.go at lines 35-38 and inspect how incomingMessages, HandleMessage, and Ack are used. Determine whether the reported pointer handling is a real bug, mitigated, or desirable behavior; the issue is complete when that classification is supported by the surrounding code.

Written by the indexing model from the issue text.