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.
When Tokio gets event notification from kevent, the pending future may
belong to a different thread. If so, it signals the other thread and
pends on kevent again. But the other thread may not have had time to
call aio_return yet. In that case, the first thread's kevent will
immediately return again.
The correct solution is to set EV_ONESHOT on the aiocb. But Rust's libc
doesn't currently expose the necessary field. Until it does, restrict
Tokio to just a single thread.
rust-lang/libc#2813