Viewing a single comment thread. View all comments

twovests wrote

I much prefer Every Other Language, where you get a stack trace that runs into the library code!

something like

some_call() failed at call another_call(x, y, z)

another_call(x,y,z) failed at internal_library(x[123])

internal_library.c failed on line 1025: index 123 is out of bounds for array x
2

flabberghaster OP wrote

You can wrap your errors though, it's not hard to do. Use fmt.Errorf() but you have to actually do it. And people tend not to where I work.

2

twovests wrote

Same situation! It's a bit more boilerplate on everything I write, but the main problem is not everyone does it.

Thankfully, now nobody writes Go at my work (^:

Unthankfully, we're language-shy because of it, lol

2