The Why, What, and How of Pinning in Rust

Jon Gjengset's stream on pin/unpin is invaluable for understanding Pin semantics: ▶ this video But the 10000 ft view is: Pin lets you tell Rust to never ever move a piece of memory. This is almost always done because the piece of memory has pointers into itself (it's self referencial) which would be come invalid if moved.

in “Effing-mad, an effect library for Rust” · View on HN

there is a chapter on async in comprehensive rust and rustbook which ought to bring you up to speed there is the async book but it is largely unfinished you can watch John Gjengset's crust of rust async, decrusting tokio, and why what, and how of pinning in rust then there are tokio-lessons and tokio tutorial which teach how to use tokio runtime and there are also good blogposts by phil-oop and rose wright on how async works [link] [link] [link] [link] [link] ▶ this video [link] [link] [link] [link]

in “Async Rust never left the MVP state” · View on HN

Let's assume for a moment self-referential references were allowed. Let's further say we have such a struct containing self-referential references and we move it. Moving actually moves things in memory, including the thing those references reference. This means the references now point at the old and now incorrect location. Accessing them would trigger undefined behavior. Self-referencing is only acceptable, if the struct is guaranteed not to move. Rust does provide a mechanism to provide such a guarantee with std::pin but outside of async code, you probably don't want to be using it. std::pin: [link] If you're curious about pinning and have a few hours to spare, ▶ this video is a great video that explains it in detail.

in “Things you can’t do in Rust (and what to do instead)” · View on HN