kori/wylt: main.go; 18 LoC

Found a possible issue in [kori/wylt](https://www.github.com/kori/wylt) at [main.go](https://github.com/kori/wylt/blob/069bed0497a40e822cbb12088d072db30450753f/main.go#L87-L104)

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.

> range-loop variable t used in defer or goroutine at line 100

[Click here to see the code in its original context.](https://github.com/kori/wylt/blob/069bed0497a40e822cbb12088d072db30450753f/main.go#L87-L104)

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

```go
for _, t := range ts {
playerLog, errs := p.Subscribe()
go func() {
for e := range errs {
// player errors are bound to fill up, should the connection be lost.
// TODO: find a better way to deal with player error logs
log.Println(e)
}
}()

for cur := range playerLog {
go func(cur playerStatus) {
fmt.Println("now playing:", cur.Track.Title, "by", cur.Track.Artist)
t.SubmitPlayingNow(cur.Track)
createTimer(p, t, cur)
}(cur)
}
}

```

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: 069bed0497a40e822cbb12088d072db30450753f

Start with main.go lines 87-104 and the linked commit, then inspect the surrounding range loop and goroutine behavior. Confirm whether the analyzer warning represents an actual bug, a mitigated case, or desirable behavior; done is a reaction with the matching classification.

Written by the indexing model from the issue text.