<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Interfaces on Nalar</title>
    <link>https://nalar.dev/tags/interfaces/</link>
    <description>Recent content in Interfaces on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/interfaces/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understand Nil Interface Values in Go</title>
      <link>https://nalar.dev/understand-nil-interface-values-in-go/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/understand-nil-interface-values-in-go/</guid>
      <description>&lt;p&gt;A Go program can print an error that looks empty, enter an &lt;code&gt;if err != nil&lt;/code&gt; branch, and still be holding a nil pointer underneath. This behavior surprises developers because it seems to violate the simple rule that &amp;ldquo;nil means no value.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;The rule is still consistent. The missing piece is that an &lt;strong&gt;interface value has two parts&lt;/strong&gt;: a dynamic type and a dynamic value. An interface is &lt;code&gt;nil&lt;/code&gt; only when neither part is set.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
