Stack traces and the errors package

[mrjn (Manish R Jain)]

@jchiu

Imagine CHECK(myFunc(…)) or err := my Func; CHECK(err)

LGTM.

@jchiu

With the stack trace, there’s less need to add context and we can cut out several “return fmt.Errorf(“blah blah blah %s”, err)”.

Can you give an example of how the code might look like with this change?

@jchiu

Creates error from within our library.

We have x/x.go for this purpose.

Note that error handling in Go is verbose by design. It’s a common complaint that newcomers have about Go. So, let’s make changes keeping that factor in mind – that it’s not a bad thing.