Why Pattern matching in switch in C Sharp (C#)? - Purpose & Use Cases

The Big Idea

What if you could replace many confusing if-else checks with one simple, clear switch statement?

The Scenario

Imagine you have a box with different types of fruits, and you want to do something special depending on the fruit type and its properties. Without pattern matching, you have to write many if-else checks, one for each fruit and condition.

The Problem

This manual way is slow and confusing. You might forget a condition or write repeated code. It's like sorting fruits by hand every time, which wastes time and causes mistakes.

The Solution

Pattern matching in switch lets you check the type and properties of an object in one clear place. It's like having a smart sorter that knows exactly what to do with each fruit type and condition, making your code neat and easy to read.

Before vs After

✗ Before

if (obj is int) { /* handle int */ } else if (obj is string s && s.Length > 5) { /* handle long string */ } else { /* default */ }

✓ After

switch (obj) { case int i: /* handle int */ break; case string s when s.Length > 5: /* handle long string */ break; default: /* default */ break; }

What It Enables

You can write clearer, shorter code that handles many cases with less chance of errors.

Real Life Example

In a game, you can easily decide what to do with different objects like enemies, items, or players by matching their types and states in one switch statement.

Key Takeaways

Manual type and condition checks are slow and error-prone.

Pattern matching in switch combines type and condition checks neatly.

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