Conditional (computer programming)

A conditional directs control flow by evaluating a Boolean expression and selecting code based on its result. The simplest form is an if statement: its body runs only when the condition is true. An if-else statement provides two mutually exclusive paths, while an else if chain tests several alternatives in sequence. Most languages use braces, indentation, or another delimiter to mark each branch.

Conditions can compare values, test object state, inspect input, or combine smaller expressions with logical operators such as AND, OR, and NOT. A conditional may appear inside another conditional, although excessive nesting can make behavior difficult to read. Good branch conditions usually express a named business or program rule rather than a dense collection of unrelated tests.

Some languages also provide a conditional expression, often written as condition ? value1 : value2. Unlike a statement, it produces a value and is useful for concise assignments and return expressions.¹

Conditional evaluation normally follows short-circuit rules, so a compound expression may stop as soon as its result is known. In an expression joined by AND, a false left operand can prevent evaluation of the right operand; with OR, a true left operand can do the same. This behavior can improve efficiency, but it also matters for safety when the skipped expression might access a missing value or perform an operation with side effects.²

Languages differ in how they represent truth. Some accept only Boolean values in conditions, whereas others convert values such as zero, an empty string, or a null reference to false. Programmers must also account for equality rules, numeric precision, nullability, and comparisons involving special values such as NaN.

For many fixed alternatives, a switch or pattern-matching construct can be clearer than a long chain of comparisons. Modern languages may match on types, ranges, destructured records, or other shapes rather than only on constant values.³

Conditional branches can affect both variable scope and the types a compiler assigns to later expressions. A variable declared inside a branch is commonly unavailable outside that branch, while languages with flow-sensitive typing may treat a value as non-null or as a narrower type after a successful test. These rules are language-specific and influence how safely conditions can guard later operations.⁴

Frequent errors include using assignment where comparison was intended, reversing a condition, omitting braces, relying on implicit truthiness, and creating an “else” that belongs to a different-looking nested if. The last problem, known as the dangling-else ambiguity, is resolved by language grammar and is often prevented by indentation or mandatory block delimiters.

Testing should cover both sides of every important condition, boundary values, combinations of independent predicates, and paths that handle invalid or unexpected input. Static analyzers and compilers can detect some unreachable branches, tautological tests, missing cases, and suspicious comparisons, but they do not replace tests of the intended rule.

Conditionals also appear outside ordinary source-level if statements, including compile-time selection, conditional compilation, guarded resource management, and pattern guards. A compiler may remove a branch whose condition is provably constant, a process called constant folding or dead-code elimination; this can improve performance but may also remove code containing unintended side effects.⁵

Some languages make exhaustive branching part of their type system. Rust, for example, requires a match expression to account for every possible value, often through an explicit wildcard arm, which helps expose unhandled cases when an enumeration changes.⁶ Other languages treat missing alternatives as runtime errors, default behavior, or compiler warnings.

Conditional logic is also central to security. Authorization checks, input validation, and feature flags are all guarded decisions, and a condition that is applied inconsistently can create a privilege or data-validation flaw. Separating policy decisions from presentation logic makes such guards easier to audit and test.

Boolean expression

An expression whose result is true or false, or is converted to one of those values by a language's rules.

Branch

One possible path of execution selected by a conditional.

Short-circuit evaluation

Evaluation of a compound Boolean expression that stops once its final result is determined.

Conditional expression

An expression that chooses between values according to a condition, rather than merely controlling statement execution.

Pattern matching

A form of conditional selection that tests the structure, type, or contents of a value.