stabilize task::yield_now #514
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
yoshuawuyts
force-pushed
the
stabilize-yield-now
branch
from
31eb2a2
to
0d5c7a2
Compare
Signed-off-by: Yoshua Wuyts <[email protected]>
ghost
approved these changes
Nov 12, 2019
|
Can we ensure that we still hold that behind a feature flag so that it doesn't accidentally land in a patch release? |
|
@skade Any reason why we shouldn't publish 1.1.0 as the next release? |
|
@stjepang Mainly as an exercise, we might have situations where we do patch releases in between. |
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.
Stabilize
task::yield_now. It doesn't perform any io, and doesn't rely on any reactor implementations either, so it can be stabilized as part of thestdfeature. Thanks!