<?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>Iterators on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/iterators/</link>
    <description>Recent content in Iterators on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Jun 2025 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/iterators/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go 1.23 Range Over Functions: What It&#39;s For and What It Isn&#39;t</title>
      <link>https://blog.turboawesome.win/2025/06/go-1.23-range-over-functions-what-its-for-and-what-it-isnt/</link>
      <pubDate>Wed, 18 Jun 2025 09:00:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2025/06/go-1.23-range-over-functions-what-its-for-and-what-it-isnt/</guid>
      <description>Go 1.23 shipped range over functions — the ability to range over an iterator function rather than a slice, map, or channel. The feature is genuinely useful for a specific class of problems and genuinely misunderstood by engineers reaching for it in places where a slice works better.</description>
    </item>
  </channel>
</rss>
