tomoya92/pybbs-go: models/Reply.go; 3 LoC

Found a possible issue in [tomoya92/pybbs-go](https://www.github.com/tomoya92/pybbs-go) at [models/Reply.go](https://github.com/tomoya92/pybbs-go/blob/307b9c9e8835b2f1cc90001c13f4326a76ee27b0/models/Reply.go#L57-L59)

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/tomoya92/pybbs-go/blob/307b9c9e8835b2f1cc90001c13f4326a76ee27b0/models/Reply.go#L57-L59)

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

```go
for _, reply := range replies {
o.Delete(&reply)
}

```

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 {Delete 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: 307b9c9e8835b2f1cc90001c13f4326a76ee27b0

Start by inspecting models/Reply.go at lines 57-59 in commit 307b9c9e8835b2f1cc90001c13f4326a76ee27b0 and review the analyzer details in this issue. Determine whether the range-loop use represents a bug, mitigated finding, or desirable behavior; done means leaving the corresponding reaction.

Written by the indexing model from the issue text.