Nick Cameron

I need to look at the offending paragraph more closely, but I suspect it should be rewritten. I think the point I was trying to make is that Rust thinks...

Given that GH can see this because it gives you the option of highlighting PRs from first-time contributors, I assume there must be API for it. Probably commit search is...

So, I think the document is not the document you want, but I'm not sure that it is the wrong document. I think what you are asking for is a...

An alternative (which I'm not sure is better) would be to use a newtype rather than an alias. The advantage would be that you could implement `lift_buf` as an inherent...

> But I believe more often than not the buffer will need to be propagated This is interesting to me - could you explain why you think it? > Then...

> Support multiple underlying memory regions. That is, the data represented by a Buffer may be backed by multiple, non contiguos memory regions. This is inspired by the [trait bytes::buf](https://docs.rs/bytes/latest/bytes/trait.Buf.html)....

I think this is a result of changing from lexical to non-lexical lifetimes, previously lifetimes would always continue to the end of explicit scopes (mostly that means to a `}`),...

In fact, we could now remove the inner `{ ... }` scope entirely.

An obvious async-ing of the sync version gives: ```rust pub trait Seek { async fn seek(&mut self, pos: SeekFrom) -> Result; async fn rewind(&mut self) -> Result { ... }...

I think it would be easy enough to extend the readiness proposal for read/write to seek. (We'd add a `SEEK` interest and the `async::Seek` trait would extend `Ready`. `seek` would...