Re:Ask HN: Why golang doesn't have ternary operator?
by kazinator on Saturday June 02, 2018 @10:07AM
(#17214635)
Lisp is unambiguous, whereas:
x = a ? b : c;
Oops; that assigns x = a, and tests it. Not if that = is that of an initializer, though: int x = a ? : b : c;
so now we have an expression that changes meaning if we have to split the initialization off into an assignment.You're often better off if you put it behind a macro:
#define IF(X, Y, Z) ((X) ? (Y) : (Z))
In C coding, a lot of ternary action happens behind the curtain of preprocessing, where expression is almost fully parenthesized.
I have no idea why GoLang doesn't have conditional expressions.
I find a conditional expression to be much easier to parse than if-else statements.
If it's too hard to read, then why is LISP written almost totally as expressions, and is still considered viable?
is much easier for me to read and understand than GoLang is supposed to be designed to remove "boilerplate code" and reduce code size, so I don't know why it doesn't have conditional expressions.Without conditional expressions, C++11 (but not C++14 and later) constexpr functions wouldn't be Turing-complete.