net: add clear_ready()
to TcpStream, UdpSocket and Unix sockets
#3716
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 change introduces
clear_ready()
similar to that in AsyncFd. Thischange allows I/O operations outside tokio to work with ready
ready()
.Motivation
#2968 (and a few followups) means to help support custom async I/O operations (#3000). However because only tokio first party I/O operations clear the ready states, as a result, readiness is not reset correctly when pairing
ready()
with I/O operations external to tokio.Solution
This change introduces
clear_ready()
similar to that inAsyncFd
to help support external I/O operations.