Re:Error stack traces in Go with x/xerror
by IshKebab on Tuesday August 24, 2021 @09:28AM
(#28288568)
I don't think so. I like that it strongly encourages you to actually add human readable context to errors too.
I think people's issue is that there's no "I don't care about errors, just show me a stack trace" option like you get with exceptions, or more or less with Rust's `?` if you don't use `.context()`.
I think people's issue is that there's no "I don't care about errors, just show me a stack trace" option like you get with exceptions, or more or less with Rust's `?` if you don't use `.context()`.