<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Borrowing on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/borrowing/</link><description>Recent content in Borrowing on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/borrowing/index.xml" rel="self" type="application/rss+xml"/><item><title>Core Concepts: Ownership, Borrowing, and Lifetimes</title><link>https://ai-blog.noorshomelab.dev/rust-guide/core-concepts-ownership-borrowing-lifetimes/</link><pubDate>Sat, 25 Oct 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/rust-guide/core-concepts-ownership-borrowing-lifetimes/</guid><description>&lt;h1 id="core-concepts-ownership-borrowing-and-lifetimes"&gt;Core Concepts: Ownership, Borrowing, and Lifetimes&lt;/h1&gt;
&lt;p&gt;This is where Rust truly distinguishes itself. Ownership, borrowing, and lifetimes are fundamental concepts that enable Rust to provide memory safety guarantees &lt;em&gt;without&lt;/em&gt; a garbage collector. Understanding these ideas is key to writing correct and efficient Rust code. While they can seem challenging at first, they become second nature with practice.&lt;/p&gt;
&lt;h2 id="ownership-rules"&gt;Ownership Rules&lt;/h2&gt;
&lt;p&gt;Every program needs to manage the memory it uses. Some languages have garbage collectors (Java, Go) that automatically clean up memory, while others require manual management (C, C++). Rust uses a unique system based on a set of rules that the compiler checks at compile time.&lt;/p&gt;</description></item><item><title>Chapter 5: Borrowing and Lifetimes: Managing References Safely</title><link>https://ai-blog.noorshomelab.dev/rust-mastery-2026/borrowing-lifetimes/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/rust-mastery-2026/borrowing-lifetimes/</guid><description>&lt;h2 id="chapter-5-borrowing-and-lifetimes-managing-references-safely"&gt;Chapter 5: Borrowing and Lifetimes: Managing References Safely&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid Rustacean! In Chapter 4, we took our first exciting dive into Rust&amp;rsquo;s unique ownership system. We learned that every piece of data in Rust has a single &amp;ldquo;owner,&amp;rdquo; and when that owner goes out of scope, the data is automatically cleaned up. This powerful concept prevents many common memory bugs, but it also means we can&amp;rsquo;t just pass data around willy-nilly without giving up ownership. As of Rust 1.94.0 (stable release checked 2026-03-20), these core memory safety principles remain fundamental.&lt;/p&gt;</description></item><item><title>Rust Mastery: Beginner to Production 2026</title><link>https://ai-blog.noorshomelab.dev/rust-mastery-2026/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/rust-mastery-2026/</guid><description>&lt;p&gt;Welcome to the ultimate learning guide for Rust, designed to take you from an absolute beginner to a master of production-grade applications by 2026. This comprehensive resource focuses on modern, practical, and industry-relevant usage, moving beyond outdated examples to equip you with essential skills. Dive deep into Rust&amp;rsquo;s core concepts like ownership, borrowing, lifetimes, and memory safety, ensuring a robust understanding of its unique approach compared to garbage-collected languages.&lt;/p&gt;</description></item></channel></rss>