You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
davidfowl
changed the title
ThreadPoolScheduler should not capture the ExecutionContext
Add UnsafeSchedule to PipeScheduler that avoids capturing the ExecutionContext
Nov 24, 2018
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
The text was updated successfully, but these errors were encountered: