<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pkg-Errors on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pkg-errors/</link>
    <description>Recent content in Pkg-Errors on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pkg-errors/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Error Handling Libraries: pkg/errors vs cockroachdb/errors vs stdlib — Complete Comparison 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-24-go-error-handling-pkg-errors-cockroachdb-stdlib-guide/</link>
      <pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-24-go-error-handling-pkg-errors-cockroachdb-stdlib-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Error handling is the most debated topic in Go. Unlike languages with try/catch exceptions, Go makes errors explicit return values — every function that can fail returns &lt;code&gt;(result, error)&lt;/code&gt;. This explicitness is Go&amp;rsquo;s strength, but it also creates challenges: how do you add context to errors as they propagate up the call stack? How do you preserve the original error for type checking? How do you attach stack traces for debugging?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
