This post is about uninitialized memory, but also about the semantics of highly optimized “low-level” languages in general. I will try to convince you that reasoning by “what the hardware d...| www.ralfj.de
This is a companion discussion topic for the Async Interviews that I am discussing. As the introductory blog post clarifies, the goal of these interviews is primarily to help answer the question, "Now that async-await is stable, what should we do next?" But it's also just to have fun talking about Async I/O and Rust and exploring what the ecosystem has to offer. Collected links to the blog posts and videos: Async Interview #1: Alex and Nick talk about async I/O and WebAssembly (video) Async ...| The Rust Programming Language Forum
API documentation for the Rust `AsyncWrite` trait in crate `futures`.| docs.rs
API documentation for the Rust `AsyncRead` trait in crate `futures`.| docs.rs
API documentation for the Rust `Stream` trait in crate `futures_core`.| docs.rs
The biggest unresolved question regarding the async/await syntax is the final syntax for the await operator. There’s been an enormous amount of discussion on this question so far; a summary of the present status of that discussion and the positions within the language team is coming soon. Right now I want to separately focus on one question which impacts that decision but hasn’t been considered very much yet: for loops which process streams.| withoutblogs
The `Read` trait allows for reading bytes from a source.| doc.rust-lang.org
A trait for objects which are byte-oriented sinks.| doc.rust-lang.org
