https://go.dev/issue/40221
- sean
On Sat, Sep 3, 2022, 16:56 Alex Besogonov wrote:
> Hi!
>
> Let me give you some context. context.Context in Go serves two main
> purposes:
> 1. Cancellation and timeout support.
> 2. A carrier of values, as a de-facto replacement for thread-local
> variables.
>
Hi!
Let me give you some context. context.Context in Go serves two main
purposes:
1. Cancellation and timeout support.
2. A carrier of values, as a de-facto replacement for thread-local
variables.
I have a problem with the first item. Cancellation and timeouts
automatically propagate to child
If you don't mind me extending the topic a bit: I bumped into a similar
issue, which I described here:
https://stackoverflow.com/questions/73591149/generics-type-inference-when-cascaded-calls-of-generic-functions
One of the solutions for the original question would be to use something
like:
ty