3 ms·
This reminds me of a comment on a Python discussion >2 years ago, of which I think often: "Whether it's computer languages or human ones, as soon as you get in
by cl3misch 4y ago
This reminds me of a comment on a Python discussion >2 years ago, of which I think often:
"Whether it's computer languages or human ones, as soon as you get into a discussion about the correct parsing of a statement, you've lost and need to rewrite in a way that's unambiguous. Too many people pride themselves on knowing more or less obscure rules and, honestly, no one else cares."
https://news.ycombinator.com/item?id=23051202 https://news.ycombinator.com/item?id=23051202
- halileohalilei 4y agoCompletely agree with that. In fact, it's the first thing I thought of when I saw the code snippet in question. Even if you replace the trigraph with the regular || operator, it's still hard to read that piece of code. Syntactic sugars and short circuits are cool and all but most of the time they have no place in production code that's meant to be read by other developers.