> 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.