Relational operators in Rust - Deep Dive

Overview - Relational operators

What is it?

Relational operators are symbols that compare two values and tell us how they relate to each other. They check if one value is equal to, greater than, less than, or not equal to another value. The result of these comparisons is always a true or false answer. This helps programs make decisions based on conditions.

Why it matters

Without relational operators, computers wouldn't know how to compare things or make choices. For example, a program couldn't tell if a number is bigger than another or if two words are the same. This would make it impossible to do tasks like sorting, filtering, or controlling what happens next in a program. Relational operators let programs react to different situations, making them smart and useful.

Where it fits

Before learning relational operators, you should understand basic data types like numbers and booleans, and how to write simple expressions. After mastering relational operators, you can learn about logical operators, control flow like if statements and loops, and how to combine conditions for complex decisions.

Mental Model

Core Idea

Relational operators compare two values and return true or false to show how they relate.

Think of it like...

It's like comparing two fruits to decide which one is bigger or if they are the same type before choosing which to eat.

  Value A   Operator   Value B
    │          │          │
    ▼          ▼          ▼
[ 5 ]   <    [ 10 ]  → true
[ apple ] == [ apple ] → true
[ 7 ]   >    [ 3 ]   → true
[ 4 ]   !=   [ 4 ]   → false

Build-Up - 6 Steps

1

Foundation

Understanding basic comparisons

Concept: Relational operators compare two values and produce a boolean result.

In Rust, relational operators include == (equal), != (not equal), < (less than), <= (less or equal), > (greater than), and >= (greater or equal). For example, 3 < 5 returns true because 3 is less than 5. These operators work with numbers, characters, and other comparable types.

Result

Using 3 < 5 returns true; 10 == 10 returns true; 7 != 7 returns false.

Understanding that relational operators always return true or false is key to using them for decisions.

2

Foundation

Relational operators with different data types

Concept: Relational operators can compare numbers, characters, and booleans where applicable.

Rust allows comparing integers like 4 > 2, characters like 'a' < 'b', and booleans with == and != only. For example, 'a' < 'b' is true because 'a' comes before 'b' in Unicode order. However, you cannot use < or > with booleans.

Result

'a' < 'b' is true; true == false is false; 5 >= 5 is true.

Knowing which types can be compared prevents errors and helps write correct code.

3

Intermediate

Using relational operators in if statements

🤔Before reading on: do you think relational operators can control program flow directly? Commit to yes or no.

Concept: Relational operators are often used inside if statements to decide which code runs.

You can write if 10 > 5 { println!("Ten is bigger"); } else { println!("Ten is not bigger"); } The condition 10 > 5 evaluates to true, so the first message prints. This shows how relational operators guide decisions.

Result

Output: Ten is bigger

Understanding that relational operators produce conditions that control program flow is essential for making programs responsive.

4

Intermediate

Combining relational operators with logical operators

🤔Before reading on: can you combine multiple relational checks in one condition? Commit to yes or no.

Concept: You can combine multiple relational expressions using logical operators like && (and) and || (or).

For example, if x > 0 && x < 10 { println!("x is between 1 and 9"); } checks if x is greater than 0 AND less than 10. Both conditions must be true for the whole to be true.

Result

If x = 5, output: x is between 1 and 9; if x = 10, no output.

Knowing how to combine conditions lets you express complex rules clearly and concisely.

5

Advanced

Relational operators with custom types

🤔Before reading on: do you think you can use relational operators on your own data types without extra work? Commit to yes or no.

Concept: Rust allows you to define how relational operators work on your custom types by implementing traits like PartialEq and PartialOrd.

For example, to compare two structs, you implement PartialEq for equality and PartialOrd for ordering. This tells Rust how to compare your data. Without these, relational operators won't work on your types.

Result

After implementing traits, you can write if obj1 < obj2 { ... } and Rust knows how to compare.

Understanding trait implementation for relational operators unlocks powerful custom comparisons in Rust.

6

Expert

Short-circuit evaluation and relational operators

🤔Before reading on: does Rust evaluate all parts of a combined condition even if the first part decides the result? Commit to yes or no.

Concept: Rust uses short-circuit evaluation with logical operators, meaning it stops checking as soon as the result is known, affecting relational operator evaluation order.

In if x > 0 && expensive_check() { ... }, if x > 0 is false, Rust skips expensive_check(). This saves time and avoids unnecessary work. Understanding this helps write efficient and safe code.

Result

expensive_check() is not called if x > 0 is false.

Knowing short-circuit behavior prevents bugs and improves performance when combining relational operators with logical ones.

Under the Hood

Relational operators in Rust are implemented as trait methods under the hood, such as PartialEq for == and PartialOrd for <, >, <=, >=. When you write a relational expression, Rust calls these trait methods to compare values. The result is a boolean value stored in memory. For primitive types, these comparisons are simple CPU instructions. For custom types, Rust calls your trait implementations. Logical operators then combine these boolean results using short-circuit logic to decide program flow.

Why designed this way?

Rust uses traits for relational operators to allow flexibility and safety. This design lets programmers define exactly how their types compare, enabling custom behavior while keeping the language consistent. It also leverages Rust's strong type system to prevent invalid comparisons at compile time. This trait-based approach replaced older, less flexible methods in other languages, making Rust safer and more expressive.

┌─────────────┐       ┌───────────────┐       ┌─────────────┐
│  Value A    │──────▶│ PartialEq /   │──────▶│  Boolean    │
│  (primitive │       │ PartialOrd    │       │  Result     │
│   or custom)│       │ trait method  │       │ (true/false)│
└─────────────┘       └───────────────┘       └─────────────┘
         │                                         │
         ▼                                         ▼
┌─────────────┐                           ┌─────────────────┐
│  Value B    │                           │ Logical Operators│
│  (primitive │                           │ (&&, ||) combine │
│   or custom)│                           │ boolean results  │
└─────────────┘                           └─────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does '==' check if two variables are the same object in memory or just equal in value? Commit to one.

Common Belief: People often think '==' checks if two variables point to the exact same object in memory.

Reality: '==' in Rust checks if the values are equal, not if they are the same object in memory.

Why it matters: Confusing value equality with identity can cause bugs when comparing complex data or references.

Quick: Can you use < or > operators on boolean values in Rust? Commit yes or no.

Common Belief: Some believe you can compare booleans with < or > to see which is 'bigger'.

Reality: Rust only allows == and != on booleans; < and > are not valid for booleans.

Why it matters: Trying to use < or > on booleans causes compile errors and confusion about boolean logic.

Quick: When combining conditions with &&, does Rust always evaluate both sides? Commit yes or no.

Common Belief: Many think Rust evaluates all parts of a combined condition regardless of earlier results.

Reality: Rust uses short-circuit evaluation and stops as soon as the result is known.

Why it matters: Misunderstanding this can lead to unexpected side effects or performance issues.

Quick: Does implementing PartialEq automatically give you < and > operators? Commit yes or no.

Common Belief: Some assume implementing PartialEq also provides ordering operators like < and >.

Reality: PartialEq only provides equality checks; PartialOrd must be implemented separately for ordering.

Why it matters: Assuming otherwise can cause compile errors or incorrect comparisons.

Expert Zone

1

Relational operators rely on traits, so their behavior can differ subtly depending on how traits are implemented for custom types.

2

Short-circuit evaluation means side effects in the second condition might not run, which can be used intentionally or cause bugs.

3

Floating-point comparisons with relational operators can be tricky due to precision and NaN values, requiring careful handling.

When NOT to use

Relational operators are not suitable for fuzzy or approximate comparisons, such as checking if two floating-point numbers are 'close enough'. In such cases, use specialized functions like 'abs(a - b) < epsilon'. Also, for complex data structures, consider custom comparison logic instead of relying solely on default traits.

Production Patterns

In real-world Rust code, relational operators are heavily used in input validation, sorting algorithms, filtering collections, and controlling program flow. Developers often implement PartialEq and PartialOrd traits for domain-specific types to enable natural comparisons. Combining relational operators with pattern matching and logical operators creates expressive and readable conditional logic.

Connections

Boolean logic

Relational operators produce boolean values that are inputs to boolean logic operations.

Understanding relational operators is essential to mastering boolean logic, as they provide the true/false values that logical operators combine.

Set theory

Relational operators correspond to membership and ordering relations in sets.

Knowing how relational operators reflect set relations helps understand sorting, filtering, and grouping in programming.

Decision making in psychology

Relational comparisons in code mirror how humans compare options to make choices.

Recognizing this connection shows how programming models human reasoning by evaluating conditions to decide actions.

Common Pitfalls

#1 Trying to use < or > on boolean values causes errors.

Wrong approach:

let a = true;
let b = false;
if a > b {
println!("a is greater");
}

Correct approach:

let a = true;
let b = false;
if a != b {
println!("a and b are different");
}

Root cause:

Misunderstanding that booleans only support equality comparisons, not ordering.

#2 Assuming all parts of a combined condition always run.

Wrong approach:

if expensive_check() && quick_check() {
// ...
}

Correct approach:

if quick_check() && expensive_check() {
// ...
}

Root cause:

Not realizing Rust stops evaluating after the first false in &&, so order matters for side effects and performance.

#3 Using == to compare floating-point numbers for exact equality.

Wrong approach:

let x = 0.1 + 0.2;
if x == 0.3 {
println!("Equal");
}

Correct approach:

let x = 0.1 + 0.2;
if (x - 0.3).abs() < 1e-10 {
println!("Close enough");
}

Root cause:

Ignoring floating-point precision issues that make exact equality unreliable.

Key Takeaways

Relational operators compare two values and always return true or false, enabling decision-making in programs.

They work with many data types but require understanding which types support which operators to avoid errors.

Combining relational operators with logical operators allows expressing complex conditions clearly.

Rust uses traits to implement relational operators, giving flexibility for custom types but requiring explicit trait implementation.

Short-circuit evaluation in Rust affects how combined conditions run, impacting performance and side effects.