Nick Cameron

Hey, this looks like a pretty cool crate! It would be nice to 'outsource' parsing to another crate, and it would be even nicer to get complete parsing. However, I...

Oh, and it means that in the future, if we're sure the above issues don't apply, then it makes it easy to remove all the custom code and just use...

I think the code just needs updating - it uses unstable features and hasn't been kept up to date recently.

Hey @NobodyXu I haven't looked in detail at the amendment above, I'm still at the information and requirements gathering stage of work on executors. But two comments: I expect using...

Some resources: * [Async vision doc](https://rust-lang.github.io/wg-async-foundations/vision/roadmap/portable/read_write.html) * [Async foundations issue](https://github.com/rust-lang/wg-async-foundations/issues/23) * [Paper doc on uninit memory](https://paper.dropbox.com/doc/IO-Buffer-Initialization-MvytTgjIOTNpJAS6Mvw38) * [Blog post on unint memory](https://blog.yoshuawuyts.com/uninit-read-write/) * [RFC 2930](https://github.com/rust-lang/rfcs/blob/master/text/2930-read-buf.md) (on extending Read trait to...

I think we have a solution to dyn-safe async traits that doesn't require 'inline' async.

ReadBuf (RFC 2930) has landed on nightly now (https://github.com/rust-lang/rust/pull/81156)

> Note that async-std also re-exports the futures-io traits From the docs, they appear to have different definitions? The async-std versions have significantly more methods. Not sure if it a...

A proposed design: https://www.ncameron.org/blog/async-read-and-write-traits/ I should flesh out the alternatives with examples and/or why they don't meet the stated goals.

> For the examples where let mut buf = [0; 1024]; is done after the ready call, ... These are simplified examples, in real life we might use one shared...