<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Raii on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/raii/</link>
    <description>Recent content in Raii on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/raii/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C&#43;&#43; RAII Scope Guards &amp; Smart Resource Handles: Boost.Scope vs Folly vs GSL vs Unique Resource</title>
      <link>https://www.pistack.xyz/posts/2026-06-29-cpp-raii-scope-guards-smart-resource-handles-boost-folly-gsl/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-29-cpp-raii-scope-guards-smart-resource-handles-boost-folly-gsl/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;RAII (Resource Acquisition Is Initialization) is C++&amp;rsquo;s cornerstone idiom for resource management — the idea that resource lifetime should be tied to object lifetime. While classes with destructors handle the common case well, there are scenarios where resources don&amp;rsquo;t naturally map to class boundaries: temporary file locks, log scopes, transaction rollbacks, and C API handles that need cleanup regardless of code path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
