Dart Relational Pattern

​

Syntax

<relational_operator> <constant_expression>

​

Mechanics and Behavior

1. Constant Requirement: The operand on the right side of the relational operator must be a compile-time constant. Variables evaluated at runtime are not permitted.
2. Static Type Safety: The Dart analyzer statically verifies that the relational operator is defined for the static type of the matched value. If the matched value is of a type that does not implement the specified operator, a compile-time error occurs.
3. Evaluation Order: When matching a value v against a relational pattern op c, the expression evaluates exactly as v op c.
4. Exhaustiveness Checking: Dart’s exhaustiveness checker does not reason about the mathematical completeness of relational patterns. Even if a set of relational patterns logically covers all possible values (e.g., < 0, == 0, > 0), the compiler cannot deduce this. A default case (such as _) is strictly required in switch expressions utilizing relational patterns to prevent a non_exhaustive_switch_expression compile-time error.

​

Code Examples

String evaluateMagnitude(int value) => switch (value) {
  < 0  => 'Negative',
  == 0 => 'Zero',
  > 0  => 'Positive',
  _    => 'Unreachable', // Required because the compiler does not evaluate relational logic for exhaustiveness
};

bool isValidPercentage(int value) {
  return switch (value) {
    >= 0 && <= 100 => true,
    _ => false,
  };
}

void checkThreshold(double temperature) {
  if (temperature case >= 100.0) {
    print('Threshold met.');
  }
}

​

Operator Overloading

class Measurement {
  final int value;
  const Measurement(this.value);

  bool operator >(Measurement other) => this.value > other.value;
}

void compareMeasurements(Measurement m) {
  // The right-hand side must be a const instantiation
  if (m case > const Measurement(50)) {
    print('Exceeds threshold');
  }
}