and-hom/gpx-cli: concat.go; 7 LoC

Found a possible issue in [and-hom/gpx-cli](https://www.github.com/and-hom/gpx-cli) at [concat.go](https://github.com/and-hom/gpx-cli/blob/77b8dae2d99f8bee6d1dadc71e7f84c1ad27e7ab/concat.go#L74-L80)

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/and-hom/gpx-cli/blob/77b8dae2d99f8bee6d1dadc71e7f84c1ad27e7ab/concat.go#L74-L80)

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

```go
for _, seg := range trk.Segments {
if (preserveSegments) {
writeXml(target, &seg)
} else {
writeXml(target, trkpts(seg.Waypoints))
}
}

```

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 {writeXml 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: 77b8dae2d99f8bee6d1dadc71e7f84c1ad27e7ab

Start with concat.go lines 74-80 in commit 77b8dae2d99f8bee6d1dadc71e7f84c1ad27e7ab, then inspect the surrounding concat flow and the writeXml calls. Determine whether the range variable usage is a bug, mitigated, or desirable behavior, and record the classification with the corresponding reaction.

Written by the indexing model from the issue text.