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

Add UnsafeSchedule to PipeScheduler that avoids capturing the ExecutionContext #27680

Closed
davidfowl opened this issue Oct 20, 2018 · 0 comments
Closed

Comments

@davidfowl
Copy link
Member

public abstract class PipeScheduler
{
    public virtual void UnsafeSchedule(Action<object> callback, object state);
}

All of the layers above the scheduler will capture and restore the ExecutionContext. We should be able to use UnsafeQueueUserWorkItem here instead. Depends on #27507

cc @pakrym @stephentoub

@davidfowl davidfowl changed the title ThreadPoolScheduler should not capture the ExecutionContext Add UnsafeSchedule to PipeScheduler that avoids capturing the ExecutionContext Nov 24, 2018
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 3.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants