4 ms·
Because nil panics on member accessors... It's the opposite of what you claim to be the standard in go. Thanks for demonstrating that you forget how to write s
by ongy 3y ago
Because nil panics on member accessors...
It's the opposite of what you claim to be the standard in go.
Thanks for demonstrating that you forget how to write software around erros.
- randomdata 3y agoWhat are you returning for error in its “junk” state, then? Clearly not nil, else by your assertion your code will panic. error has member accessors you will call - Error() if nothing else. Methinks you’ve not thought this through. What’s it about the word error that trips up programmers like this?