Why pattern matching matters in C Sharp (C#) - Performance Analysis

Time Complexity: Why pattern matching matters

O(n)

Understanding Time Complexity

When using pattern matching in C#, it is important to understand how it affects the speed of your program.

We want to know how the time to check patterns grows as we add more cases or more complex patterns.

Scenario Under Consideration

Analyze the time complexity of this pattern matching example.

string Describe(object obj) {
    return obj switch {
        int i => $"Integer {i}",
        string s => $"String {s}",
        null => "Null value",
        _ => "Unknown type"
    };
}
    

This code checks the type of an object and returns a description based on the pattern matched.

Identify Repeating Operations

Look at what repeats when matching patterns.

• Primary operation: Checking each pattern case one by one.
• How many times: Up to the number of patterns until one matches.

How Execution Grows With Input

As you add more pattern cases, the program may check more before finding a match.

Number of Patterns (n)	Approx. Checks
3	Up to 3 checks
10	Up to 10 checks
100	Up to 100 checks

Pattern observation: The number of checks grows linearly with the number of patterns.

Final Time Complexity

Time Complexity: O(n)

This means the time to find a matching pattern grows in direct proportion to how many patterns you have.

Common Mistake

[X] Wrong: "Pattern matching always runs in constant time because it looks simple."

[OK] Correct: Each pattern is checked one after another until a match is found, so more patterns mean more checks.

Interview Connect

Understanding how pattern matching scales helps you write efficient code and explain your choices clearly in interviews.

Self-Check

What if we used a dictionary lookup instead of switch pattern matching? How would the time complexity change?

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