Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostTaskPropagation: Explore .NET or other experience with token propagation #7

Open
jyasskin opened this issue Jan 27, 2020 · 1 comment
Labels
context propagation Related to the currentTaskSignal proposal

Comments

@jyasskin
Copy link
Member

https://docs.microsoft.com/en-us/dotnet/standard/parallel-programming/attached-and-detached-child-tasks#cancellation-and-child-tasks says that .NET's cancellation system doesn't provide anything like scheduler.currentTaskSignal for getting the current Task's cancelation token. This may be evidence that it's not needed, or there may be evidence out on the web that .NET developers find this frustrating. It'd be good to figure out which way that evidence goes.

@shaseley shaseley added the context propagation Related to the currentTaskSignal proposal label Jun 30, 2021
@shicks
Copy link

shicks commented Nov 8, 2021

Another important consideration is the challenges faced by https://github.com/legendecas/proposal-async-context

Specifically, I want to make sure we don't expose a half-baked solution that fails to meet some key requirements, such as allowing user-space pooling. At the very least, we need to make sure we learn from past attempts. This is a very hard problem to get right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
context propagation Related to the currentTaskSignal proposal
Projects
None yet
Development

No branches or pull requests

3 participants