Why Go Rejects the Ternary Operator and How to Write Clear Conditional Code

The ternary operator (?:) is common in many languages such as Python, JavaScript, and C/C++:

val = trueValue if expr else falseValue  // Python
const val = expr ? trueValue : falseValue  // JavaScript
const char *val = expr ? "trueValue" : "falseValue";  // C/C++

Go does not support this operator; attempting to write val := expr ? "trueValue" : "falseValue" results in a compilation error because ? is an invalid character.

The reason ?: is absent from Go is that the language's designers had seen the operation used too often to create impenetrably complex expressions. The if‑else form, although longer, is unquestionably clearer. A language needs only one conditional control flow construct.

Go’s design philosophy of simplicity prefers using the existing if statement instead of adding new syntax.

Complex ternary expressions can become hard to read, for example:

const status = (type===1?(again===1?'再售':'已售'):'未售');

Converting this to if statements improves clarity:

let status = '';
if (type === 1) {
    if (again === 1) {
        status = '再售';
    } else {
        status = '已售';
    }
} else {
    status = '未售';
}

For simple value assignments, a ternary expression is concise and readable, especially with arrow functions:

const func = (age) => age > 18 ? '成年人' : '未成年人';

Go can emulate a ternary using a helper function, though it is not recommended due to performance overhead, required type assertions, and eager evaluation of arguments:

func If(cond bool, a, b interface{}) interface{} {
    if cond { return a }
    return b
}
age := 20
val := If(age > 18, "成年人", "未成年人").(string)

Pros of the ternary operator:

Clearer for short expressions after getting used to its linear style.

Eliminates intermediate variables, reducing mental load.

Fewer side effects, making code easier to track.

Cons of the ternary operator:

Readability suffers for complex logic.

Can be overused as a replacement for proper if statements.

Branches must be single expressions, not multiple statements.

In summary, whether to use a ternary operator depends on the specific case; in Go, the preferred approach is to stick with if statements for clarity and simplicity.