Nick Cameron
Nick Cameron
To be a little more concrete, the read traits would look something like ```rust pub trait Read { async fn read(&mut self, buf: &mut [u8]) -> Result; async fn read_buf(&mut...
> Honestly, while the trait Read is indeed portable, it might not have the best performance, especially for completion based async io-engine such as io-uring. Sorry, somewhat unspoken here, but...
These are good questions, but they are somewhat off-topic for this issue. I have proposed adding a BufWrite trait and perhaps OwnedWrite too, though I've mostly been focussing on reading....
> I was under the impression this signature had changed to buf: ReadBufMutWrapper for the 'soundness questions' (eg mem::replace()). Did I miss this getting vetoed or was this just a...
> "Some users have stronger preferences for performance or memory usage over ergonomics (this is multiple groups [...]" — Which groups are these? Why do they have these preferences? Do...
No, and there are _a lot_ of changes
There are at least unsafe warnings, which are currently commented out for Rust (too many false positives)
1) a 2) There is nothing special about the `match`, it is about destructuring in patterns, e.g., ``` let x = &&42; // x: &&i32 let y = x; //...
and `#[cfg(...)]`
> Can anyone come up with examples where these two interpretations would be in conflict? The obvious case is where the function returns something in the implementation which is not...