4 ms·

How so? I’m not that familiar with Go anymore.

• hyperhopper 1y ago
  Search any Go codebase for err != nil, for starters.
  • olivia-banks 11mo 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 11mo ago
      > 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.