Could this crate also define AsyncRead and AsyncWrite equivalents using the new types?

[FrankReh]

Would it be appropriate for this crate to also define equivalents of AsyncRead and AsyncWrite?

I was curious which concrete buffer types would make up the input and output, and how the implicitly returned read or write length parameter is gleaned.

[nrc]

Yes, sort of. There is a design for async Read and Write traits using this buffer, specifically for io_uring, iocp, and similar: https://github.com/nrc/portable-interoperable/tree/master/io-traits#owned-read. The concrete buffer type is up to the user. The length parameter is going to be the filled length in the owned buffer (if it is not possible how to get that, then it might be a bug in the design.)

[FrankReh]

Thanks for the link.