<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sync.Cond on Nalar</title>
    <link>https://nalar.dev/tags/sync.cond/</link>
    <description>Recent content in Sync.Cond 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/sync.cond/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go sync.Cond Wait Rechecks Shared State</title>
      <link>https://nalar.dev/go-sync-cond-wait-rechecks-shared-state/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/go-sync-cond-wait-rechecks-shared-state/</guid>
      <description>&lt;p&gt;&lt;code&gt;sync.Cond.Wait&lt;/code&gt; resumes after a notification, but the notification does not assert that a caller-specific condition is still true when the goroutine reacquires the lock. The shared predicate remains the source of truth, so a waiter checks it again after every return from &lt;code&gt;Wait&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This boundary separates notification from state. &lt;code&gt;Signal&lt;/code&gt; and &lt;code&gt;Broadcast&lt;/code&gt; announce that relevant state may have changed; they do not transfer ownership of that state or reserve it for a particular waiter.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
