Question 1

How do I add key-value details to errors in Go using emperror/errors?

Accepted Answer

Use the WithDetails or WrapWithDetails functions to attach key-value pairs to errors. For example, errors.WithDetails(err, "user_id", 123) adds structured context that can be extracted later for enhanced debugging and logging.

Question 2

Is emperror/errors a drop-in replacement for github.com/pkg/errors?

Accepted Answer

Yes, it is designed as a drop-in replacement, providing all the same functions like Wrap and Cause, plus additional features like structured details. You can replace the import with minimal code changes.

Question 3

Emperror/errors vs standard library errors: which should I use?

Accepted Answer

Use emperror/errors if you need stack traces, structured details, or multi-error support for better debugging. Stick with the standard library if you only require basic error handling to avoid extra dependencies and overhead.

Question 4

Can I use emperror/errors with Go versions before 1.13?

Accepted Answer

Yes, it backports Go 1.13 error handling features like Is and As, so it's compatible with Go 1.12 and above, as indicated by the Go version badge in the README.

Question 5

How to handle multiple errors at once in Go using emperror/errors?

Accepted Answer

Use the multi-error feature to aggregate errors into a single value. This simplifies handling scenarios where multiple issues occur, such as in validation loops or concurrent goroutines, by returning one combined error.

Question 6

What are the performance costs of using emperror/errors?

Accepted Answer

The main costs come from stack trace generation and error wrapping, which increase memory usage and can slow down error creation. For performance-critical code, consider using NewPlain for errors without stack traces or benchmarking your specific use case.

errors

What is errors?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions