Thomas de Zeeuw

Instead of a RawFd.

Currently we can only enable direct descriptor during the configuration in the ring (via `Config::with_direct_descriptors`). This is about enabling support later on, e.g. via `Ring`.

Current `Signals` has the following two methods: * `Signals::receive` -> returns a single signal. * `Signals::receive_signals` -> returns multiple signals. Rename them to: * `Signals::receive` -> returns multiple signals. *...

Currently some Futures own a SubmissionQueue, others take a reference to it. It would be to have a mechanism where we can support both. Maybe it's a simple as adding...

At the time of writing the `AsyncFd` is an fd and a `SubmissionQueue`. An fd is 4 bytes (`i32`) and `SubmissionQueue` is an `Arc`, so a pointer of 8 bytes...

Fd creating Futures leak fds when dropped

1

For example the `net::Socket` and `net::Accept` futures both leak the created file description if they are not completed, but the operation is.

Not sure what the API would look like, maybe something like the following: ```rust fn chain((&mut Fut1, &mut Fut2, &mut Fut2)) -> Chain; struct Chain { futures: Futs, } impl...

Use io::ErrorKind::ResourceBusy for QueueFull

1

Depends on the unstable [`io_error_more`](https://github.com/rust-lang/rust/issues/86442) feature. Effectively reverting commit fd798960cc4306d7d8700375fd7f76cb01c34a0e.

Don't submit needless submission in SubmissionQueue::wake

2

The current `SubmissionQueue::wake` implementation always adds an event, even if we're not currently polling. We can try to keep track when we're polling and only then add a submission, otherwise...

Indication that more data was left to read in a socket.