3 ms·

I've also worked on codebases that have overused the && operator. Should we remove that in favor of nested if?

• stcredzero 10y ago
  Only if the cost-benefit works out, and there isn't a better solution.
  • pcwalton 10y ago
    And that's clearly the case with generics.
    • stcredzero 10y ago
      You're seriously saying that generically? All languages should simply have them? Not so sure you should dismiss the context like that.
      • aikah 10y ago
        > You're seriously saying that generically? All languages should simply have them? Not so sure you should dismiss the context like that. Point me to a successful statically typed language born after 2005 that doesn't have some form of generics. Go has generics by the way, you just can define your own in user land, which is a stupid limitation.