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.
The core idea is to
abusemake use of the fact that Rust'sasync/await
syntax desugars into a state machine that implements Future to instead implement the simple state machines required for a sans I/O API. To achieve this I'm stashing some shared state in theWaker
used by I/O loop implementations thatNineP
impls can access using arequest_bytes
macro. Under the hood this macro is just awaiting a custom future that pulls the waker out of its poll context and stashes the requested number of bytes before returningPoll::Pending
. In the I/O loop this value is read, I/O is performed and then the requested data is stored back in the shared state before polling again. When theRequestBytes
future is polled again it takes the bytes out of the shared state and returns it as its result to theNineP::read
impl.