Back to list

Expensive error wrapping and stack trace overhead

5/10 Medium

Error wrapping up the call stack and garbage collection of intermediate objects is nearly as expensive as try-catch, yet requires manual coding. Stack traces provide redundant information most of the time and lack a mechanism to toggle them.

Go
Category
performance
Workaround
none
Stage
build
Freshness
persistent
Scope
language
Upstream
wontfix
Recurring
No

Sources

Collection History

Query: “What are the most common pain points with Go for developers in 2025?”3/29/2026

In Go, wrapping each error with another error up the entire call stack, and then garbage collecting all the created objects is almost as expensive. Stacked traces can be very useful... but the rest of the time they're highly expensive redundant information.

Created: 3/29/2026Updated: 3/29/2026