I imagine the reality lies somewhere in between the two extreme takes that you present here.
> is a problem nearly as old as Go itself It's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.
[dead]
I imagine the reality lies somewhere in between the two extreme takes that you present here.
> is a problem nearly as old as Go itself It's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.
[dead]