Enable the portable thread pool by default in coreclr #43841
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkotas
approved these changes
Oct 26, 2020
Member
|
@tommcdon per our discussion last week, want to ensure the eventing issue doesnt cause any debugger issues you were alluding to. |
stephentoub
approved these changes
Oct 26, 2020
Contributor
Author
|
Reverted the last commit, back to the original simple commit. CI issues seen so far are being fixed in #43888. |
Member
|
Happy to see this go in! |
Contributor
Author
|
CI didn't seem to pick up some of the changes from the other PR, rebased to latest |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Would like to give it some bake time, enable it in some previews, and allow for further experimentation with that implementation. There is some work left to do with events as captured by #38763, it is expected that they would be fixed in the .NET 6 time-frame.