https://blog.youkuaiyun.com/qq_42632945zh-cnhttps://blog.youkuaiyun.com/https://blog.youkuaiyun.com/qq_42632945/article/details/167702506https://blog.youkuaiyun.com/qq_42632945/article/details/167702506qq_42632945Mon, 12 Oct 2026 20:55:18 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/164339385https://blog.youkuaiyun.com/qq_42632945/article/details/164339385qq_42632945Thu, 03 Sep 2026 20:00:51 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/164304171https://blog.youkuaiyun.com/qq_42632945/article/details/164304171qq_42632945Wed, 02 Sep 2026 20:39:37 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/164096846https://blog.youkuaiyun.com/qq_42632945/article/details/164096846qq_42632945Wed, 26 Aug 2026 21:05:06 +0800 与 Pin<&mut T> 的契约关系，解释 Pin 如何通过限制普通 &mut T 的获取来封堵安全代码中的移动入口。文章进一步结合 async 状态机说明 Future::poll 为什么需要 pinned receiver，并通过手动投影和 pin-project 的宏展开，分析结构化投影、条件 Unpin、析构约束及其背后的 unsafe 证明责任。]]>https://blog.youkuaiyun.com/qq_42632945/article/details/144944708https://blog.youkuaiyun.com/qq_42632945/article/details/144944708qq_42632945Sun, 05 Jan 2025 13:51:04 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/142926564https://blog.youkuaiyun.com/qq_42632945/article/details/142926564qq_42632945Mon, 14 Oct 2024 19:38:16 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/136357336https://blog.youkuaiyun.com/qq_42632945/article/details/136357336qq_42632945Wed, 28 Feb 2024 22:15:33 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/136356865https://blog.youkuaiyun.com/qq_42632945/article/details/136356865qq_42632945Wed, 28 Feb 2024 21:37:19 +0800https://blog.youkuaiyun.com/qq_42632945/article/details/135135448https://blog.youkuaiyun.com/qq_42632945/article/details/135135448qq_42632945Thu, 21 Dec 2023 17:20:56 +0800