Introduce async-dispatcher runtime feature #191
Merged
Conversation
This file contains 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
This allows us to use ZeroMQ with native schedulers instead of relying directly on Tokio or async-std's `spawn`. Co-Authored-By: Kyle <[email protected]> Co-Authored-By: Max <[email protected]>
rgbkrk
force-pushed
the
async-dispatcher-feature
branch
from
1e6e84e
to
6d9ce5a
Compare
This was referenced May 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
async-dispatcherallows us to use ZeroMQ with native schedulers instead of relying directly on Tokio or async-std'sspawn.As for why, Zed uses native OS schedulers for async work.