completion

Note: My interest in this crate has now been superseded by my proposal for asynchronous destructors and a Leak trait. I no longer think this design is the best way to achieve completion futures.

Utilities for writing completion-based asynchronous code.

A completion future is a future that must be run to completion, unlike regular futures which can be dropped and stopped at any time without the future's knowledge. This allows for more flexibility for the implementer of the future and allows APIs like io_uring and IOCP to be wrapped in a zero-cost way.

This is based off this RFC by Matthias247.

Features

• std: Enables features that require the standard library, on by default.
• alloc: Enables features that require allocation, on by default.
• macro: Enables the completion, completion_async, completion_async_move and completion_stream macros, on by default.

License: MIT OR Apache-2.0

lib.rs:

Macro to generate completion-based async functions and blocks. This crate shouldn't be used directly, instead use completion.