<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>たまのブログ</title>
    <link>https://eggpan.net/en/</link>
    <description>Recent content on たまのブログ</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>ja</language>
    <lastBuildDate>Tue, 17 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://eggpan.net/en/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I built a library to handle stack traces nicely in Go</title>
      <link>https://eggpan.net/en/post/go-stackprune-errors/</link>
      <pubDate>Tue, 17 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://eggpan.net/en/post/go-stackprune-errors/</guid>
      <description>When writing error handling code in Go, you often want stack traces — but there aren&amp;rsquo;t many libraries that provide them in a nice, practical way.
For example:
 pkg/errors allows multiple errors.Wrap calls, but stack traces get duplicated. The maintenance has stopped, and newer APIs like errors.Join are not supported. cockroachdb/errors is well-designed, but the amount of information it outputs can be overwhelming and often requires additional processing.  With these challenges in mind, I created my own error handling library: stackprune/errors.</description>
    </item>
    
  </channel>
</rss>
