This seems reasonable. The only question is, when can it be merged?

@leaxoy storing the Context as a member on a struct is an anti-pattern in Go, so I'd need to find another way to pass this information along. I had some thoughts about how to approach this with the async eval draft PR, but haven't had a chance to return to it.

In #557, you mentioned the use of the callback channel directly.

Also, in Kubernetes it seems to be more common to store the callback channel.

Just propagating the done channel to function overloads would at least allow cancellation propagation (which was the initial objective of this MR), while removing the context embedding. We could then have a wrapper of the channel respecting context.Context interface for overloads.

I might be able to propose something for this if you're good with that @TristonianJones