Rust Futures explained

Series of articles and blog post that helps understanding Rust's futures.
Related Topics:

Rust Streams

A discussion on HTTP streaming in Rust and some related crates.
Rust streamsAs Rust’s async story is evolving, so is Rust’s streaming story. In this post we’ll take a look at how Rust’s streaming model works, how to use it effectively, and where things are heading in the future. Surf: an asynchronous cross-platform streaming HTTP client for RustAnnouncement of Surf, an asynchronous cross-platform streaming HTTP client for Rust. This project was a collaboration between Kat Marchán (Entropic / Microsoft), Stjepan Glavina (Ferrous Systems), and Yoshua Wuyts. SurfSurf is a friendly HTTP client built for casual Rustaceans and veterans alike. It’s completely modular, and built directly for async/await. Whether it’s a quick

Rust’s Pin API

The reasoning behind Pin API and some articles that shade light on its evolutionary process.
Pin API in Rust coreA Pin<P> ensures that the pointee of any pointer type P has a stable location in memory, meaning it cannot be moved elsewhere and its memory cannot be deallocated until it gets dropped. We say that the pointee is “pinned”. The Rust RFC Book: PinIntroduce new APIs to libcore / libstd to serve as safe abstractions for data which cannot be safely moved around. Pin APIs (RFC 2349)Tracking issue for Pin APIs (RFC 2349) #49150 Standard library API for immovable typesStandard library API for immovable types #2349 Async/Await I: Self-Referential StructsWhy we need Pin api? The