<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>WaitGroup on Nalar</title>
    <link>https://nalar.dev/tags/waitgroup/</link>
    <description>Recent content in WaitGroup 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/waitgroup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go WaitGroup Reuse Requires Completed Wait Boundaries</title>
      <link>https://nalar.dev/go-waitgroup-reuse-requires-completed-wait-boundaries/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/go-waitgroup-reuse-requires-completed-wait-boundaries/</guid>
      <description>&lt;p&gt;A &lt;code&gt;sync.WaitGroup&lt;/code&gt; can be reused after a wait phase completes, but a new independent task set cannot begin while calls to &lt;code&gt;Wait&lt;/code&gt; from the prior phase are still active. The boundary is the return of every earlier &lt;code&gt;Wait&lt;/code&gt;, not merely the instant at which the internal task counter reaches zero.&lt;/p&gt;&#xA;&lt;p&gt;This constraint matters when one &lt;code&gt;WaitGroup&lt;/code&gt; instance is retained across batches, epochs, request waves, or repeated coordination cycles. Reuse is supported, but phases must not overlap at the zero-to-positive counter transition.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
