Why pattern matching matters in C Sharp (C#) - Visual Breakdown

Concept Flow - Why pattern matching matters

Input value

↓

Match pattern 1?

No→Match pattern 2?

↓

Execute action 1

↓

Done

The program checks the input against patterns one by one and runs the matching action, making code clearer and safer.

Execution Sample

C Sharp (C#)

object obj = 42;
switch (obj)
{
  case int i:
    Console.WriteLine($"Integer {i}");
    break;
  default:
    Console.WriteLine("Unknown type");
    break;
}

This code checks if obj is an int and prints it; otherwise, it prints 'Unknown type'.

Execution Table

Step	Input Value	Pattern Checked	Match Result	Action Taken	Output
1	42 (int)	case int i	Yes	Print Integer 42	Integer 42
2	42 (int)	default	No	No action

💡 Pattern matched at step 1, so switch ends after executing that case.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
obj	42 (int)	42 (int)	42 (int)	42 (int)
i	undefined	42	undefined	42

Key Moments - 3 Insights

Why does the switch stop after the first matching pattern?

Because once a pattern matches (see execution_table step 1), the corresponding action runs and the switch exits to avoid running other cases.

What if the input doesn't match any pattern?

The default case runs (execution_table step 2 shows no match for int, so default would execute), ensuring the program handles unexpected inputs safely.

Why use pattern matching instead of if-else?

Pattern matching makes code clearer and safer by combining type checks and variable extraction in one step, as shown by the concise match and action in the sample.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'i' after step 1?

A 42

B undefined

C null

D 0

💡 Hint

Check variable_tracker row for 'i' after step 1.

At which step does the pattern match successfully?

A Step 2

B No match

C Step 1

D Both steps

💡 Hint

See execution_table 'Match Result' column.

If obj was a string instead of int, which action would run?

A Print Integer value

B Default case action

C No action

D Error thrown

💡 Hint

Default case runs when no pattern matches, see execution_table step 2.

Concept Snapshot

Pattern matching checks a value against patterns in order.
When a pattern matches, its code runs and the check stops.
It combines type check and variable extraction.
Default case handles unmatched values.
This makes code clearer and safer than many if-else checks.

Full Transcript

Pattern matching in C# lets you check a value against different patterns and run code for the first match. The flow starts with an input value, then checks each pattern in order. If a pattern matches, the program runs the related action and stops checking further. If no pattern matches, the default case runs. This approach is clearer and safer than many if-else statements because it combines type checking and variable extraction in one step. For example, if the input is an integer 42, the pattern 'case int i' matches, assigns 42 to i, and prints it. If the input was not an int, the default case would print 'Unknown type'. This helps avoid errors and makes code easier to read and maintain.