Re:Gopher Wrangling. Effective error handling in Go
by marcus_holmes on Monday June 19, 2023 @09:13PM
(#36398531)
Surprised that the "always wrap your errors" rule isn't in there. It's been the rule in the last few Go teams I've been in.
[ Parent
| on HN ]
Re:Gopher Wrangling. Effective error handling in Go
by AlexCoventry on Monday June 19, 2023 @09:33PM
(#36398670)
We moved away from wrapping them recently for performance reasons.
Re:Gopher Wrangling. Effective error handling in Go
by za3faran on Monday June 19, 2023 @09:52PM
(#36398784)
How much of a performance hit were they causing?
Re:Gopher Wrangling. Effective error handling in Go
by lanstin on Monday June 19, 2023 @09:58PM
(#36398834)
and how many errors are they getting?
Re:Gopher Wrangling. Effective error handling in Go
by sethammons on Tuesday June 20, 2023 @06:02AM
(#36401837)
You got to add more context here. An entire blog post would be worthy. We do some very performant code at high scale and error wrapping has never put pressure on our systems. Highly interested in what you saw.
Re:Gopher Wrangling. Effective error handling in Go
by preseinger on Tuesday June 20, 2023 @08:10AM
(#36402900)
what programs are you writing where error wrapping represents a performance cost that's worth avoiding???
Re:Gopher Wrangling. Effective error handling in Go
by stephen123 on Tuesday June 20, 2023 @12:20AM
(#36399671)
It seems like a waste of time to me. Wrapping errors adds context. But you can usually get enough context from stack traces.