<?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>Rust on AWP Developer Blog</title>
    <link>https://andrewpauluhn.dev/tags/rust/</link>
    <description>Recent content in Rust on AWP Developer Blog</description>
    <image>
      <title>AWP Developer Blog</title>
      <url>https://andrewpauluhn.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://andrewpauluhn.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.145.0</generator>
    <language>en</language>
    <lastBuildDate>Thu, 13 Mar 2025 01:28:11 -0600</lastBuildDate>
    <atom:link href="https://andrewpauluhn.dev/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rust Iterators: Balancing efficiency with readability</title>
      <link>https://andrewpauluhn.dev/posts/efficient_rust_iterators/</link>
      <pubDate>Thu, 13 Mar 2025 01:28:11 -0600</pubDate>
      <guid>https://andrewpauluhn.dev/posts/efficient_rust_iterators/</guid>
      <description>&lt;p&gt;One of my favorite things about Rust, and one of the first things that attracted me to it, is its iterators and the many &lt;a href=&#34;https://doc.rust-lang.org/reference/glossary.html#combinator&#34;&gt;combinator&lt;/a&gt; functions that are available.&lt;/p&gt;
&lt;p&gt;Before getting into Rust, I was focused on Typescript/JavaScript, and I had a preference for &lt;code&gt;.filter()&lt;/code&gt;, &lt;code&gt;.map()&lt;/code&gt; and &lt;code&gt;reduce()&lt;/code&gt; in lieu of manual loops. I already had a disposition for function composition, method chaining and closures.&lt;/p&gt;
&lt;p&gt;Anyone who has read the Rust Book might have seen the statement in the section on &amp;ldquo;Loops vs. Iterators&amp;rdquo;:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
