futures-io: Use nightly-only core::io - #3033
Open
bushrat011899 wants to merge 1 commit into
Open
Conversation
rustbot
added
A-io
bushrat011899
force-pushed
the
futures_io_no_std
branch
from
August 4, 2026 11:48
9d2745f to
5df5313
Compare
bushrat011899
force-pushed
the
futures_io_no_std
branch
from
August 4, 2026 11:55
5df5313 to
798aaba
Compare
Author
|
I'm pretty sure the Miri failure is unrelated to this PR? |
This was referenced Aug 4, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Implements
no_stdsupport behind a new rustflagfutures_unstable_nightly_core_ioby relying on the unstable nightlycore_iofeature. This allows targets such aswasm32v1-noneto use the async traits in this crate. Please see rust-lang/rust#154046 for details on tracking issue.Notes