<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Runtime Semantics on Nalar</title>
    <link>https://nalar.dev/tags/runtime-semantics/</link>
    <description>Recent content in Runtime Semantics on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/runtime-semantics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Garbage Collection Does Not Close External Resources</title>
      <link>https://nalar.dev/garbage-collection-does-not-close-external-resources/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/garbage-collection-does-not-close-external-resources/</guid>
      <description>&lt;p&gt;An object can become unreachable while a file descriptor, socket, database transaction, or operating-system lock associated with it still has a meaningful external lifetime. Garbage collection can reclaim managed memory after reachability disappears. It does not, by that fact alone, perform the protocol operation that releases an external resource.&lt;/p&gt;&#xA;&lt;p&gt;The distinction is structural. A collector reasons about references inside a managed heap. A resource such as a file descriptor is an entry maintained by the operating system, and a database transaction is state maintained by another component. Their release semantics come from APIs and protocols outside the collector&amp;rsquo;s reachability model.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
