Closed ashtonian closed 12 months ago
Thanks for picking this up (I generally update to the latest version of Go pretty quickly so did not notice).
Just want to consider whether this is the best approach or if we should replace the use of AfterFunc
with an alternative (generally want to support the current and previous versions of Go and not require users to be running the latest).
I've suggested an alternative approach that retains 1.20 compatibility.
Describe the bug
context.AfterFunc()
wasn't introduced until v1.21 - I think that means it needs to be reflected in the go mod?