SethHafferkamp/GoRSS: feedparsing/exports.go; 6 LoC

Found a possible issue in [SethHafferkamp/GoRSS](https://www.github.com/SethHafferkamp/GoRSS) at [feedparsing/exports.go](https://github.com/SethHafferkamp/GoRSS/blob/c56d5e4544ff8f6f09bb840d7a148480ab3d7743/feedparsing/exports.go#L49-L54)

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/SethHafferkamp/GoRSS/blob/c56d5e4544ff8f6f09bb840d7a148480ab3d7743/feedparsing/exports.go#L49-L54)

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

```go
for _, feedUrl := range feedUrls {
feedUrl.LastKickoffDate = &[]time.Time{time.Now()}[0]
db.Save(&feedUrl)
newJob := ParseJob{feedUrl: feedUrl.FeedUrl, feedId: int(feedUrl.ID)}
jobs <- newJob
}

```

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 {Save 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: c56d5e4544ff8f6f09bb840d7a148480ab3d7743

Inspect feedparsing/exports.go at lines 49-54 and read the analyzer output about the range-loop pointer and Save call. Trace the relevant usage and decide whether the finding represents a Bug, Mitigated case, or Desirable Behavior, then record that classification on the issue.

Written by the indexing model from the issue text.