https://www.rustbites.com/tags/pin/Recent content in Pin on rustbitesHugoenWed, 27 May 2026 10:43:13 +0200https://www.rustbites.com/posts/bite-162/Tue, 26 May 2026 17:00:00 +0100https://www.rustbites.com/posts/bite-162/<p>Self-referential structs are the obvious &ldquo;this should work but doesn&rsquo;t&rdquo; pattern in Rust: a struct that holds a buffer plus a reference into that buffer falls apart the moment it moves and the reference dangles. <code>Pin&lt;P&gt;</code> is the type that says &ldquo;the pointee is fixed in memory&rdquo; — and is the reason every <code>async fn</code> future you&rsquo;ve ever <code>.await</code>ed can keep a pointer to its own local variables.</p>https://www.rustbites.com/posts/bite-164/Tue, 26 May 2026 17:00:00 +0100https://www.rustbites.com/posts/bite-164/<p>The moment you hand-roll <code>Future::poll</code>, you have a <code>Pin&lt;&amp;mut Self&gt;</code> and a question Rust won&rsquo;t answer for you: how do I touch my fields? <code>self.inner</code> doesn&rsquo;t compile, <code>&amp;mut self.inner</code> is what <code>Pin</code> exists to prevent, and the answer — <em>pin projection</em> — is one of those idioms everyone reinvents until they reach for <code>pin-project-lite</code>.</p>