Use the ternary operator (? :) for simple conditional assignments with two outcomes, as it enables concise inline logic but should be avoided when nested. 2. Apply null coalescing (??) to safely handle null values and provide defaults, especially useful for configuration, fallbacks, and optional inputs, noting it only checks null—not falsy values. 3. Utilize match expressions for clean, type-safe value mapping with strict comparison and no fall-through, ideal for replacing switch statements or complex conditionals while returning a value directly. Choose the right construct based on clarity and context, prioritizing readability over cleverness.

When writing clean, readable, and efficient code, relying solely on if-else statements can quickly lead to bloated and hard-to-maintain logic—especially when dealing with simple conditional assignments or value resolution. Modern programming languages offer more concise and expressive tools: ternary operators, null coalescing, and match expressions. These constructs help reduce verbosity and improve clarity when used appropriately.

Let’s explore how to move beyond traditional if-else chains by leveraging these powerful alternatives.

1. Ternary Operator: Simple Conditional Assignment

The ternary operator (condition ? valueIfTrue : valueIfFalse) is ideal for assigning a value based on a boolean condition—without needing multiple lines.

Instead of:

if ($userLoggedIn) {
    $status = 'active';
} else {
    $status = 'guest';
}

Use:

$status = $userLoggedIn ? 'active' : 'guest';

This keeps the logic inline and focused, especially useful in return statements or variable initialization.

? Best for: simple, one-level conditionals with two outcomes.
? Avoid for: nested or complex logic (e.g., ? : ? : chains), which hurt readability.

Tip: If you find yourself nesting ternaries, it’s time to step back and consider if-else or match.

2. Null Coalescing: Safely Handle Missing Values

The null coalescing operator (??) returns the left operand if it exists and is not null; otherwise, it returns the right. It's perfect for default values.

Instead of:

$username = isset($_GET['user']) ? $_GET['user'] : 'anonymous';

Use:

$username = $_GET['user'] ?? 'anonymous';

Even better: PHP supports chained null coalescing:

$displayName = $user['name'] ?? $user['username'] ?? 'Guest';

This avoids repeated isset() checks and makes intent clearer.

? Best for: fallbacks, configuration defaults, optional parameters.
? Works with arrays, object properties, and function returns (if wrapped).

Note: Unlike ternary, ?? only checks for null, not falsy values like 0, '', or false. So:

echo '' ?? 'default';  // outputs: '' (empty string is not null)
echo '' ?: 'default';  // outputs: 'default' (falsy check via ternary)

Know the difference between ?? and ?:.

3. match Expressions: Type-Safe, Expression-Based Switching

Introduced in PHP 8, match is a modern alternative to switch. It’s an expression, meaning it returns a value—and it uses strict type comparison.

Instead of:

switch ($httpStatus) {
    case 200:
    case 304:
        $statusText = 'success';
        break;
    case 404:
        $statusText = 'not found';
        break;
    case 500:
        $statusText = 'server error';
        break;
    default:
        $statusText = 'unknown';
}

Use:

$statusText = match ($httpStatus) {
    200, 304 => 'success',
    404 => 'not found',
    500 => 'server error',
    default => 'unknown',
};

Key advantages:

• No break statements (no fall-through).
• Returns a value directly.
• Strict comparison (won’t match '200' as integer 200 unless cast).
• Cleaner syntax and fewer bugs.

You can even use conditions in arms (via expression matching):

$result = match (true) {
    $x < 0 => 'negative',
    $x > 0 => 'positive',
    default => 'zero',
};

? Best for: mapping values to results, replacing complex ternaries or switches.
? Not for: side effects or long procedural blocks.

When to Use What?

Don’t force one tool everywhere. The goal is clarity, not minimalism.

Final Thoughts

Moving beyond if-else isn’t about eliminating it—it’s about choosing the right tool for the job. Ternary, null coalescing, and match each excel in specific scenarios where brevity and expressiveness matter.

Use them to:

• Reduce boilerplate
• Improve readability
• Prevent common bugs (like missing break)

But remember: simple and clear always beats clever.

Basically, just know when to reach for each one—and when to stick with good old if.

The above is the detailed content of Beyond if-else: Leveraging Ternary, Null Coalescing, and match Expressions. For more information, please follow other related articles on the PHP Chinese website!