Why pattern matching matters in C Sharp (C#) - The Real Reasons

The Big Idea

What if you could replace messy type checks with clean, readable code that just works?

The Scenario

Imagine you have a box full of different toys: cars, dolls, blocks, and puzzles. You want to find all the cars and play with them. Without a clear way to check each toy's type, you have to pick up each one, guess what it is, and then decide what to do. This takes a lot of time and can be confusing.

The Problem

Manually checking each toy means writing many if-else statements or switch cases that get long and messy. It's easy to make mistakes, like missing a toy type or mixing up actions. This slows you down and makes your code hard to read and fix.

The Solution

Pattern matching lets you quickly and clearly check what kind of toy you have and decide what to do with it in one simple step. It makes your code shorter, easier to understand, and less error-prone by directly matching the shape or type of data.

Before vs After

✗ Before

if (obj is Car) { /* play with car */ } else if (obj is Doll) { /* play with doll */ } else { /* other toys */ }

✓ After

switch (obj) { case Car car: /* play with car */ break; case Doll doll: /* play with doll */ break; default: /* other toys */ break; }

What It Enables

Pattern matching unlocks clear, concise, and powerful ways to handle different data types and shapes in your code, making complex decisions simple and safe.

Real Life Example

In a game, you might have different characters like warriors, mages, and archers. Pattern matching helps you quickly decide how each character attacks without writing long, confusing code.

Key Takeaways

Manual type checks are slow and error-prone.

Pattern matching simplifies and clarifies decision-making.

It makes your code easier to read, write, and maintain.

Practice

1. What is the main benefit of using pattern matching in C#?

easy

A. It simplifies checking types and extracting data in one step.

B. It makes the program run faster by optimizing CPU usage.

C. It automatically fixes syntax errors in the code.

D. It replaces all loops with recursive calls.

Solution

1. Step 1: Understand pattern matching purpose

   Pattern matching lets you check a variable's type and extract its data in a single, clear step.

2. Step 2: Compare with other options

   Options A, B, and D describe unrelated or incorrect benefits not provided by pattern matching.

3. Final Answer:

   It simplifies checking types and extracting data in one step. -> Option A

4. Quick Check:

   Pattern matching = Simplifies type checks [OK]

Hint: Pattern matching combines type check and data use in one step [OK]

Common Mistakes:

• Thinking pattern matching speeds up CPU performance
• Confusing pattern matching with syntax error fixing
• Believing pattern matching replaces loops

2. Which of the following is the correct syntax for pattern matching with is in C#?

easy

A. if (obj is int number) { /* use number */ }

B. if (obj is int) number { /* use number */ }

C. if (obj is int: number) { /* use number */ }

D. if (obj int is number) { /* use number */ }

Solution

1. Step 1: Recall correct pattern matching syntax

   The correct syntax uses is Type variable inside the if condition, like obj is int number.

2. Step 2: Identify syntax errors in other options

   Options A, B, and C have incorrect order or punctuation that cause syntax errors.

3. Final Answer:

   if (obj is int number) { /* use number */ } -> Option A

4. Quick Check:

   Correct pattern matching syntax = if (obj is int number) { /* use number */ } [OK]

Hint: Remember: 'is Type variable' is the pattern matching syntax [OK]

Common Mistakes:

• Placing variable before type in 'is' expression
• Using colon ':' instead of space
• Mixing order of keywords

3. What will be the output of this code?

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

medium

A. String: 42

B. Integer: 42

C. Unknown type

D. Compilation error

Solution

1. Step 1: Identify the type of obj

   obj is assigned the integer value 42, so its runtime type is int.

2. Step 2: Match switch cases

   The switch matches case int i because obj is an int, so it prints "Integer: 42".

3. Final Answer:

   Integer: 42 -> Option B

4. Quick Check:

   obj is int 42, so output = "Integer: 42" [OK]

Hint: Match the runtime type to the correct case in switch [OK]

Common Mistakes:

• Assuming obj is string because of quotes missing
• Thinking default case runs first
• Confusing compile-time and runtime types

4. Identify the error in this pattern matching code:

object obj = "hello";
if (obj is int number)
{
    Console.WriteLine(number);
}

medium

A. The variable 'number' is not declared before use.

B. The 'is' keyword cannot be used with variables.

C. Missing braces around the if block.

D. The pattern matching condition will never be true for a string.

Solution

1. Step 1: Analyze the type of obj

   obj holds a string "hello", but the pattern checks if obj is an int.

2. Step 2: Understand pattern matching behavior

   Since obj is a string, the condition obj is int number is false, so the block never runs.

3. Final Answer:

   The pattern matching condition will never be true for a string. -> Option D

4. Quick Check:

   obj is string, pattern checks int, so condition false [OK]

Hint: Check if variable type matches pattern type before using it [OK]

Common Mistakes:

• Assuming variable 'number' must be declared separately
• Thinking 'is' cannot be used with variables
• Ignoring that condition can be false without error

5. Given a list of objects List<object> items = new() { 1, -2, "two", 3.0, null };, which pattern matching expression correctly counts only the positive integer values?

hard

A. items.Count(item => item is string s)

B. items.Count(item => item is int)

C. items.Count(item => item is int number && number > 0)

D. items.Count(item => item != null)

Solution

1. Step 1: Understand the goal

   We want to count only positive integers in the list, ignoring other types and null.

2. Step 2: Analyze each option

   items.Count(item => item is int) counts all ints but does not filter by value; items.Count(item => item is int number && number > 0) counts ints greater than 0, which matches positive integers; items.Count(item => item is string s) counts strings; items.Count(item => item != null) counts all non-null items.

3. Step 3: Choose the best option

   items.Count(item => item is int number && number > 0) uses pattern matching with a condition to count only positive integers, which is a precise use of pattern matching.

4. Final Answer:

   items.Count(item => item is int number && number > 0) -> Option C

5. Quick Check:

   Pattern matching with condition filters integers correctly [OK]

Hint: Use 'is Type var && condition' to filter precisely [OK]

Common Mistakes:

• Counting all ints without condition when needed
• Counting strings or non-null items by mistake
• Not using variable in pattern matching for conditions