<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Memory on Learning Journal</title><link>https://learning-notes-8ef.pages.dev/tags/memory/</link><description>Recent content in Memory on Learning Journal</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://learning-notes-8ef.pages.dev/tags/memory/index.xml" rel="self" type="application/rss+xml"/><item><title>Rust Ownership: Mental Models That Finally Clicked</title><link>https://learning-notes-8ef.pages.dev/posts/programming/rust-ownership/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://learning-notes-8ef.pages.dev/posts/programming/rust-ownership/</guid><description>&lt;h2 id="the-problem-rust-solves"&gt;The Problem Rust Solves&lt;/h2&gt;
&lt;p&gt;Memory bugs — use-after-free, double-free, dangling pointers — are the root of most systems security vulnerabilities. Rust eliminates them at compile time.&lt;/p&gt;
&lt;h2 id="the-three-rules"&gt;The Three Rules&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Every value has exactly one owner.&lt;/li&gt;
&lt;li&gt;When the owner goes out of scope, the value is dropped.&lt;/li&gt;
&lt;li&gt;Ownership can be transferred (moved) or temporarily lent (borrowed).&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="what-finally-clicked"&gt;What Finally Clicked&lt;/h2&gt;
&lt;p&gt;I stopped thinking about the borrow checker as a restriction and started thinking about it as a guarantee: &lt;strong&gt;there is always exactly one place responsible for cleanup&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>