<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pin-Project on rustbites</title><link>https://www.rustbites.com/tags/pin-project/</link><description>Recent content in Pin-Project on rustbites</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 27 May 2026 10:43:13 +0200</lastBuildDate><atom:link href="https://www.rustbites.com/tags/pin-project/index.xml" rel="self" type="application/rss+xml"/><item><title>164. Pin projection — How to actually use the fields behind Pin&lt;&amp;mut Self&gt;</title><link>https://www.rustbites.com/posts/bite-164/</link><pubDate>Tue, 26 May 2026 17:00:00 +0100</pubDate><guid>https://www.rustbites.com/posts/bite-164/</guid><description>&lt;p&gt;The moment you hand-roll &lt;code&gt;Future::poll&lt;/code&gt;, you have a &lt;code&gt;Pin&amp;lt;&amp;amp;mut Self&amp;gt;&lt;/code&gt; and a question Rust won&amp;rsquo;t answer for you: how do I touch my fields? &lt;code&gt;self.inner&lt;/code&gt; doesn&amp;rsquo;t compile, &lt;code&gt;&amp;amp;mut self.inner&lt;/code&gt; is what &lt;code&gt;Pin&lt;/code&gt; exists to prevent, and the answer — &lt;em&gt;pin projection&lt;/em&gt; — is one of those idioms everyone reinvents until they reach for &lt;code&gt;pin-project-lite&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>