Extract rayon-futures as a separate crate #436
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
|
I think we should go ahead and do this soon, since the core additions are still |
cuviper
force-pushed
the
factor-out-futures
branch
from
7030282
to
ddd2369
Compare
cuviper
force-pushed
the
factor-out-futures
branch
from
ddd2369
to
a14568c
Compare
|
I added more CI fixes, and finally we're green again! Merging... |
This was referenced Sep 16, 2017
Closed
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.
This is a rebase of #344, also moving the
futuressupport to a separaterayon-futurescrate. No other changes were made to the actual code.