News for hackers. Stuff that matters.
Re:Overview of Rust error handling libraries by TheDong on Friday November 22, 2019 @12:04PM (#21607475)
Every time you use `fmt.Errorf` and `if err != nil { return nil, err }`, you're returning a stringly typed error up the stack.

The entire stdlib does this. An error stack is never present from stdlib functions' errors, and third party libraries I see it just as infrequently.

If only novice go devs do that, than the entire go core team are novices, as well as the authors of popular go projects like kubernetes and docker.

Re:Overview of Rust error handling libraries by skybrian on Friday November 22, 2019 @02:45PM (#21609288)
"Stringly typed" means literally a string. Go doesn't always distinguish between errors, but the error type does distinguish errors from non-errors and that's important.

It seems better to have coarse-grained types than to standardize the wrong type hierarchy?