https://nalar.dev/tags/memory-safety/ Recent content in Memory Safety on Nalar Hugo en-us Thu, 03 Sep 2026 00:00:00 +0700 https://nalar.dev/understand-pin-and-unpin-in-rust/ Thu, 03 Sep 2026 00:00:00 +0700 https://nalar.dev/understand-pin-and-unpin-in-rust/ <p>Most Rust values can move freely. Assign a value to another variable, pass it by value, return it from a function, or replace it inside a container, and the value may end up at a different memory address.</p> <p>Usually that is exactly what you want. Rust&rsquo;s ownership model tracks who owns a value, not where that value must remain in memory.</p> <p>A smaller class of types is different. Some values become <strong>address-sensitive</strong>: code relies on the value continuing to exist at the same memory location. Compiler-generated futures and carefully designed self-referential structures are common examples.</p>