Question 1

How do I use tracerr with existing Go errors?

Accepted Answer

Wrap existing errors using tracerr.Wrap(err) to attach stack traces; if the error is nil, it remains nil, ensuring safe usage. For new errors, use tracerr.New or tracerr.Errorf.

Question 2

Tracerr vs pkg/errors: which is better for Go error handling?

Accepted Answer

Tracerr excels with source code fragments and colorized output for development visibility, while pkg/errors is more established for stack traces and integrates tightly with Go's error wrapping. Choose tracerr for richer debugging context.

Question 3

Can I customize how many lines of source code tracerr shows?

Accepted Answer

Yes, functions like PrintSource allow specifying line ranges, e.g., PrintSource(err, 5, 2) for 5 lines before and 2 after the error line, offering flexibility in detail level.

Question 4

Is tracerr suitable for production environments?

Accepted Answer

While performance-optimized, the added overhead of stack traces might be unnecessary in production where logs are aggregated; it's best used in development or for detailed debugging in staging.

Question 5

How does tracerr handle nil errors?

Accepted Answer

tracerr.Wrap(nil) returns nil, and printing functions handle nil gracefully, preventing crashes and aligning with Go's error handling idioms to avoid unnecessary noise.

Question 6

Can I integrate tracerr with logging libraries like zap or logrus?

Accepted Answer

Yes, use Sprint functions to capture error output as strings, then pass them to logging libraries. However, colorization may be lost in structured logs, so consider disabling it for production.

tracerr

What is tracerr?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions