> Not sure what go debugging is like but I imagine you can quickly work your way to the first err!=nil while debugging. How do you imagine that happening? I ca

> Not sure what go debugging is like but I imagine you can quickly work your way to the first err!=nil while debugging. How do you imagine that happening? I can’t see another way then either stepping through your code or setting breakpoints on all the ‘return nil, err’ statements. You rarely, if ever, can use a ‘watch variable’ feature, because each function will have its own local ‘err’, and will have a new one on each invocation. If, instead of ‘return buil, err’, there’s ‘throw new…’ in such blocks, I don’t see why you couldn’t do the same things.