chore(core): Align Reader and Writer's API design #4498
Merged
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.
Align the Reader and Writer's API design as mentioned in #4465
into_futures_io_async_read
tointo_futures_async_read
.into_futures_io_async_write
tointo_futures_async_write
.into_std_io_read
tointo_std_read
.The context is clear that we don't need to re-mention
io
in our API.into_futures_bytes_stream
tointo_bytes_stream
into_std_bytes_iterator
tointo_bytes_iterator
There is only one widely used stream API so far. Remove
futures
to make API more clear.