<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Rust on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/rust/</link>
		<description>Recent content in Rust on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 21 Jul 2026 18:36:07 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/rust/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rust Ownership and Borrowing: A Practical Mental Model</title>
				<link>https://www.compilemymind.com/posts/rust-ownership-borrowing-practical-mental-model/</link>
				<pubDate>Tue, 21 Jul 2026 11:47:15 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/rust-ownership-borrowing-practical-mental-model/</guid>
				<description>&lt;p&gt;Rust uses ownership rules to manage resources without requiring a garbage collector for ordinary memory safety. Each value has an owner, assignment or function calls can move ownership, and references let code borrow a value without taking ownership. The compiler checks these relationships, which means many errors are best understood as questions about who owns a value, how long a borrow lasts, and whether mutation could overlap another access.&lt;/p&gt;&#xA;&lt;h2 id=&#34;a-working-model-for-rust-ownership-and-borrowing-a-practical-mental-model&#34;&gt;A working model for Rust Ownership and Borrowing: A Practical Mental Model&lt;/h2&gt;&#xA;&lt;p&gt;For each short example, label the owner, every move, each immutable or mutable borrow, and the final use of each variable. Predict which line should compile before running the compiler. Use a String or Vec for resource-owning behavior and a simple Copy scalar as a contrast. Keep lifetime syntax out of the first pass; the goal is to understand the data flow that lifetime annotations later describe.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
