recovic/imitate-zhihu: service/QuestionService.go; 14 LoC

Found a possible issue in [recovic/imitate-zhihu](https://www.github.com/recovic/imitate-zhihu) at [service/QuestionService.go](https://github.com/recovic/imitate-zhihu/blob/9cb013432249eeb063da60ede1a92ecc9b614154/service/QuestionService.go#L20-L33)

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/recovic/imitate-zhihu/blob/9cb013432249eeb063da60ede1a92ecc9b614154/service/QuestionService.go#L20-L33)

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

```go
for _, question := range questions {
res = cache.ReadQuestionCounts(&question)
if res.NotOK() {
return nil, res
}

questionDto := dto.QuestionShortDto{}
model.Copy(&questionDto, &question)

questionDto.Creator, _ = GetUserProfileByUid(question.CreatorId)

tool.CutContent(&questionDto.Content, 80)
questionDtos = append(questionDtos, questionDto)
}

```

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 {Copy 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: 9cb013432249eeb063da60ede1a92ecc9b614154

Start with service/QuestionService.go at lines 20-33 and review the range-loop usage shown in the report. Follow the analyzer's referenced call context to determine whether the pointer handling is a real bug, mitigated, or desirable behavior. Done means leaving the appropriate Bug, Mitigated, or Desirable Behavior reaction.

Written by the indexing model from the issue text.