Learn About Pattern Matching In C#

Introduction

 

In this article, we are going to discuss pattern matching, introduced in C# 7.0 and improved in C#8.0 and C# 9.0. This article can be very useful for beginners, intermediates, and professionals.

 

What is Pattern Matching?

 

A question that comes to mind before we start with pattern matching is: 

 

What are we using for matching data in C#? The answer is,  If/else condition or switch/case statement.

 

If/else and switch/case condition have the limitation of comparing a defined member variable with primitive data types only and that creates the requirement of Pattern matching.

 

Pattern matching in C# 7.0

 

C# 7.0 introduces the wonderful feature “Pattern matching” with the below case.

• If/else
• Switch/Case

Let’s use the below code to understand pattern matching in C# 7.0.

 

Before C# 7.0, if we wanted to calculate the area of a Rectangle and Circle, we had to write the below code.

using System;

namespace PatternMatching
{
    class Program
    {
        static void Main(string[] args)
        {
            Rectangular r1 = new Rectangular { Width = 12.34, Height = 56.12 };
            Rectangular r2 = new Rectangular { Width = 56.34, Height = 56.34 };

            Circle c1 = new Circle { Redius = 34.56 };

            CalculateArea(r1);
            CalculateArea(r2);
            CalculateArea(c1);

            Console.ReadLine();
        }

        public static void CalculateArea(Figure f)
        {
            if(f is Rectangular)
            {
                // Perform Conversion as parent class can not access member of child class directly.
                Rectangular rec = f as Rectangular;
                Console.WriteLine("Area of Rectangular {0}", rec.Width * rec.Height);
            }
            else if(f is Circle)
            {
                Circle Cir = f as Circle;
                Console.WriteLine("Area of Circle {0}", Circle.pi * Cir.Redius * Cir.Redius);
            }
        }
    }
    public class Figure
    {
        public const float pi = 3.14f;
    }
    public class Circle : Figure
    {
        public double Redius { get; set; }
    }
    public class: Figure
    {
        public double Width { get; set; }
        public double Height { get; set; }
    }
}

Output

 

In the above code, we have created three classes

• Figure – Parent Class
• Rectangular – Child class inherited from parent class Figure
• Circle – Child class inherited from parent class Figure

We have method class, CalculateArea, which is used to calculate the area of a Rectangle or Circle.

 

As rectangular and circle have different formulates for calculating area. Hence, we have to follow the below steps to calculate the area in before C# 7.0, 

1. if condition to know figure “is” Rectangular or Circle
2. Then we have to use “as” for explicit conversation.
3. Calculate and CalculateArea.

Now we will write the same code in C# 7.0. 

public static void CalculateArea(Figure f) {
    if (f is Rectangular rec) Console.WriteLine("Area of Rectangular {0}", rec.Width * rec.Height);
    else if (f is Circle Cir) Console.WriteLine("Area of Circle {0}", Circle.pi * Cir.Redius * Cir.Redius);
}

The above code is an example of Pattern Matching in C#7.0. In the code, we have removed explicit class conversion code which makes the code simpler and clearer.

 

Switch/Case -Pattern matching

 

Same code with Switch/case in C# 7.0

public static void CalculateArea(Figure f) {
    switch (f) {
        case Rectangular rec:
            Console.WriteLine("Area of Rectangular {0}", rec.Width * rec.Height);
            break;
        case Circle Cir:
            Console.WriteLine("Area of Circle {0}", Circle.pi * Cir.Redius * Cir.Redius);
            break;
    }
}

You might notice that in the above code that we do not need comparison using the “is” keyword and conversion using the “as” keyword.

 

Let's discuss the below line of code, 

Rectangular r2 = new Rectangular { Width = 56.34, Height = 56.34 };

Width and Height are the same, which means this is square and not rectangular. Let's implement square logic now,

public static void CalculateArea(Figure f) {
    switch (f) {
        case Rectangular rec when rec.Width == rec.Height:
            Console.WriteLine("Area of Rectangular {0}", rec.Width * rec.Height);
            break;
        case Rectangular rec:
            Console.WriteLine("Area of Rectangular {0}", rec.Width * rec.Height);
            break;
        case Circle Cir:
            Console.WriteLine("Area of Circle {0}", Circle.pi * Cir.Redius * Cir.Redius);
            break;
    }
}

In the first case statement, we are doing a comparison using when. This is one of the powerful features of pattern matching.

 

Pattern Matching in C# 8.0

 

In C# 8.0, switch expression is introduced. It is not a Switch case but a switch expression.

 

The main difference between the Switch case and Switch Expression is, a switch expression is a way to return a specific value based on another value.

 

Switch expression can be used with Tuple. If you want to learn about tuple please go through the article.

 

We will try to implement the same example using C# 8.0 

public static void CalculateArea(Figure f) {
    var value = f
    switch {
        Rectangular rec_ when rec_.Width == rec_.Height => rec_.Width * rec_.Height;
        Rectangular rec_ => rec_.Width * rec_.Height,
            Circle cir_ => Circle.pi * cir_.Redius * cir_.Redius,
            _ =>
            throw new NotImplementedException()
    };
    Console.WriteLine("Areaf  {0}", value);
}

The switch expression doesn’t have a case statement. It is easy to write compare to the switch case.

 

Pattern Matching in C# 9.0

 

Relational patterns and Logical pattern combinators were introduced with C# 9.0, and you can use them not only with is expressions but also in switch expressions. Also, it has improved in Type Pattern matching.

 

We will start with improvement in Type Pattern matching.

 

Type pattern

 

See the below code, 

public static bool IsCircle(Figure f) => f
switch {
    Circle _ => true,
        Rectangular _ => false,
        _ =>
        throw new NotImplementedException()
};

The above function will return true if the figure is a circle and false in the case of a rectangle. 

 

Let’s observe the below line of code, 

Circle _ => true,

We need _ in the case where we are not using an object at all. Underscore (_) is required in c# 8.0 but not required in c# 9.0.

 

There is no big change in functionality, but it is a very important code, cleaning-wise.

 

Same code in C# 9.0,

public static bool IsCircle(Figure f) => f
switch {
    Circle => true,
        Rectangular => false,
        _ =>
        throw new NotImplementedException()
};

Relation Pattern Matching

 

To understand the Relation pattern, consider that we have a member class and we need to perform some calculation based on Member age.

using System;
namespace PatternMatching {
    class Program {
        static void Main(string[] args) {
            var member = new Member {
                Age = 45
            };
            Console.WriteLine("Charges : {0}", ChargesCalculate(member));
            Console.ReadLine();
        }
        static double ChargesCalculate(Member m) => m.Age
        switch {
            >= 25 => 350, < 25 => 350,
        };
        public class Member {
            public int Age {
                get;
                set;
            }
        }
    }
}

ChangesCalculate method is calculated changes based on age. If age is greater or equal to 25 then changes would be 350 else 250. This method can be worked in only .Net (C# 9.0), and not working in C# 8.0. This is something new introduced in C# 9.0.

 

That’s all for this article. Hope you enjoy this article.