top | item 45854686 (no title) hyperhopper | 3 months ago Search any Go codebase for err != nil, for starters. discuss order hn newest olivia-banks|3 months ago Well, sure, but this is a problem nearly as old as Go itself. I thought they were referring to larger more recent things, like how generics work, or something to that effect. galvatron9k|3 months ago > is a problem nearly as old as Go itselfIt's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.
olivia-banks|3 months ago Well, sure, but this is a problem nearly as old as Go itself. I thought they were referring to larger more recent things, like how generics work, or something to that effect. galvatron9k|3 months ago > is a problem nearly as old as Go itselfIt's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.
galvatron9k|3 months ago > is a problem nearly as old as Go itselfIt's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.
olivia-banks|3 months ago
galvatron9k|3 months ago
It's as old as C. C and Go are the only two significant languages which end up constantly checking for errors like this.