> And from what I've read they are better than Rusts coroutines for this use case
Reference please? In what sense are they better, and what makes them better?
Reference please? In what sense are they better, and what makes them better?
When a Future is aborted early, it's destroyed immediately with no remorse. This means it can't simply offer its own buffers to the kernel, because the kernel could write back after the Future has been freed.
An API contract that includes "just be careful not to do the stupid thing" is not good enough by Rust's standards, so the only way to guarantee safety would be to have Future's destructor wait synchronously until the I/O operation is cancelled on the kernel side, but that's inelegant in an async context.
However that is not a general property of c++ coroutines. The generator style coroutines also seem randomly cancellable