In Jim's Personal Opinion

Extended Error Use Case: calm

Mon, 23 Mar 2026 00:00:00 +0000

Let’s build the calm package to leverage our errclass and stacktrace packages

Extended Error Logging

Tue, 17 Mar 2026 00:00:00 +0000

Recap
#

We have created a high-level ExtendedError type, and we implemented slog.LogValuer with the following code:

func (e ExtendedError[T]) LogValue() slog.Value {
 return slog.GroupValue(
 slog.Any("error", e.err),
 slog.Any("data", e.Data),
 )
}

Each of our sub-packages (errclass, errcontext, and stacktrace) also implement slog.LogValuer. This allows us to add details to our logs easily.

Problem Description
#

Consider the following program:

Extended Error Use Case: stacktrace

Mon, 16 Mar 2026 00:00:00 +0000

Recap
#

At the start of this series, we created a generic error wrapper that allowed us to attach type-safe data to another error.

The important parts we will need to reference are:

package xerrors

type ExtendedError[T any] struct {
 err error
 Data T
}

func Extend[T any](data T, err error) error { ... }
func Extract[T any](err error) (T, bool) { ... }

One of the stated reasons for doing this was to allow structured logging of errors to easily contain additional structured data. In this article, we will further explore that particular use case with a new sub-package.

Jim Wood

Mon, 09 Mar 2026 00:00:00 +0000

Jim Wood


	519-998-0694
	jimwood1337@gmail.com
	linkedin.com/in/woodjp
	github.com/wood-jp
	jimsopinion.xyz

Overview
#

Backend software engineer with over a decade of professional experience designing and implementing complex, interconnected systems across multiple stakeholder groups. Primary language is Go, with hands-on experience in distributed systems, event-driven architectures, blockchain infrastructure, and real-time data pipelines. Proven ability to lead technical initiatives from research through production, often at startups where wearing many hats is the norm.

Extended Error Use Case: errcontext

Wed, 25 Feb 2026 00:00:00 +0000

Recap
#

At the start of this series, we created a generic error wrapper that allowed us to attach type-safe data to another error.

The important parts we will need to reference are:

package xerrors

type ExtendedError[T any] struct {
 err error
 Data T
}

func Extend[T any](data T, err error) error { ... }
func Extract[T any](err error) (T, bool) { ... }

Extended Error Use Case: errclass

Fri, 20 Feb 2026 00:00:00 +0000

Let’s build the errclass package on top of the generic error wrapper created previously.

A Generic Go Custom Error Wrapper

Tue, 03 Feb 2026 00:00:00 +0000

Let’s build a custom error that uses generics to add type-safe sidecar data.

Typical First Post

Sun, 25 Jan 2026 00:00:00 +0000

Welcome to my blog. As is tradition, this first post talks about the intent of the blog as a whole.

In Jim's Personal Opinion

Extended Error Use Case: calm

Extended Error Logging

Recap #

Problem Description #

Extended Error Use Case: stacktrace

Recap #

Jim Wood

Overview #

Extended Error Use Case: errcontext

Recap #

Extended Error Use Case: errclass

A Generic Go Custom Error Wrapper

Typical First Post

Recap
#

Problem Description
#

Recap
#

Overview
#

Recap
#