<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Concurrency on Andrew Odendaal</title>
    <link>https://andrewodendaal.com/tags/concurrency/</link>
    <description>Recent content in Concurrency on Andrew Odendaal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 22 Mar 2025 08:00:00 +0400</lastBuildDate>
    <atom:link href="https://andrewodendaal.com/tags/concurrency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Concurrency in Rust: Fearless Parallelism</title>
      <link>https://andrewodendaal.com/rust-concurrency/</link>
      <pubDate>Sat, 22 Mar 2025 08:00:00 +0400</pubDate>
      <guid>https://andrewodendaal.com/rust-concurrency/</guid>
      <description>&lt;p&gt;Concurrency is notoriously difficult to get right. Race conditions, deadlocks, and other concurrency bugs are among the most insidious issues in software development, often manifesting only under specific timing conditions that are hard to reproduce and debug. Rust tackles this challenge head-on with a concurrency model that leverages the type system and ownership rules to prevent data races and other concurrency errors at compile time.&lt;/p&gt;&#xA;&lt;p&gt;In this comprehensive guide, we&amp;rsquo;ll explore Rust&amp;rsquo;s approach to concurrency, from basic threads to advanced asynchronous programming. You&amp;rsquo;ll learn how Rust&amp;rsquo;s ownership system enables &amp;ldquo;fearless concurrency&amp;rdquo;—the ability to write concurrent code with confidence that the compiler will catch common mistakes before they become runtime bugs. By the end, you&amp;rsquo;ll have a solid understanding of how to build efficient, safe concurrent applications in Rust.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
