<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Determinism on Nalar</title>
    <link>https://nalar.dev/tags/determinism/</link>
    <description>Recent content in Determinism on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/determinism/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Map Iteration Order Is Not Stable</title>
      <link>https://nalar.dev/go-map-iteration-order-is-not-stable/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/go-map-iteration-order-is-not-stable/</guid>
      <description>&lt;p&gt;A &lt;code&gt;range&lt;/code&gt; over a Go map can visit the same entries in a different order on consecutive iterations. The language specification leaves map iteration order unspecified and gives no guarantee that a later pass over an unchanged map will repeat an earlier sequence.&lt;/p&gt;&#xA;&lt;p&gt;That contract is stronger than saying that maps are merely unsorted. An unsorted container could still expose a stable insertion-dependent or storage-dependent sequence. A Go program cannot assign such meaning to map traversal.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
