20 July 2017
Every new version of C# language specification brings us something tasty to try, something that makes the developer’s life easier and the code more clean and understandable. Fortunately, version 7.0 is not an exception! With the following description, I’d like to show one of the great new features in C# 7.0 - Pattern Matching. In this article we will go through the new syntax in depth and see on the real examples how to use pattern matching and how it actually works.
With C# 7.0 we get a new conception of patterns. We can describe them as special language elements that help check values for specific characteristics and extract them.
Right now, pattern matching can be used in two existing language constructions: switch-case, and is. The patterns themselves can have the form of constants and types. Additionally, when type patterns are used, the checked value can be immediately saved into a variable.
Let’s demonstrate all the new stuff with real examples. Previously we did the following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | class Animal { } class Cat : Animal { public void Meow() { } } void DemoCat(Animal obj) { // Check that passed obj is a Cat by casting. Use it if not null. var cat = obj as Cat; if (cat != null) { cat.Meow(); } } |
Here we check passed obj value against type (type pattern). With the new syntax the same can be done much easier:
1 2 3 4 5 6 7 | void DemoCat(Animal obj) { if (obj is Cat cat) { cat.Meow(); } } |
From now we can do constant pattern matching:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | void DemoString(string str) { if (str is "Hello World") { // ... } } void DemoInt(int num) { if (num is 100) { // ... } } |
But wait, there’s more! We can use a constant pattern when we don’t know the exact object type:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | void DemoObject(object obj) { if (obj is "Hello World") { // ... } if (obj is 100) { // ... } if (obj is DayOfWeek.Friday) { // ... } if (obj is null) { // ... } } |
New possibilities naturally combine together:
1 2 3 4 5 6 7 | static void DemoParse(object obj) { if (obj is string str && int.TryParse(str, out int num)) { Console.WriteLine(num); } } |
Just look at this beautiful code! And imagine what you would have to write without the new syntax. :/
Ok. Now it should be clear. But the interesting thing is what happens inside. Let’s compile and decompile it to understand how it actually looks without the syntax sugar:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 | void DemoString(string str) { if (Equals("Hello World", str)) { // ... } } void DemoInt(int num) { if (Equals(100, num)) { // ... } } void DemoObject(object obj) { if (Equals("Hello World", obj)) { // ... } if (Equals(100, obj)) { // ... } if (Equals(DayOfWeek.Friday, obj)) { // ... } if (Equals(null, obj)) { // ... } } void DemoParse(object obj) { string s = obj as string; int result; if (s != null && int.TryParse(s, out result)) { Console.WriteLine(result); } } |
Everything is quite simple, but it’s ugly…
In the example above, in the method DemoCat, we used a reference type. But what happens if we do pattern matching against a value type?
1 2 3 4 5 6 7 | void DemoValueType(object obj) { if (obj is int num) { // ... } } |
A value type cannot be used with the operator ‘as’ and cannot be translated the same way in the background as it was with the reference Cat object. But anyway, the new syntax somehow allows us to do the check, and it looks the same. And what actually happens is:
1 2 3 4 5 6 7 8 9 | static void DemoValueType(object obj) { int? nullable = obj as int?; int valueOrDefault = nullable.GetValueOrDefault(); if (nullable.HasValue) { // ... } } |
The compiler translates the matching expression through the nullable type.
Let’s move further. We can see more interesting examples when pattern matching is used in the switch-case construction. In the old version, only constants were allowed near the case and the switch itself supported only enums, strings and base types like int, bool, char, etc.
The following example demonstrates different kinds of pattern matching in the switch-case construction and its new features:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | void Demo(object obj) { switch (obj) { // Match different kinds of constants: case 10: Console.WriteLine("int const"); break; case "Hello World": Console.WriteLine("string const"); break; case null: Console.WriteLine("Argument is null"); break; // Match the type. Note, that variable _ is not used, however it is needed even // when you want to check only the type. case Cat _: Console.WriteLine("Argument is Cat"); break; // Match reference type and value type with conditions: case string str when str.Length > 10 && str != "Hello World": Console.WriteLine(str); break; case long num when num > 0 && num < 1000: Console.WriteLine(num); break; // Combined cases: case string str when int.TryParse(str, out int num) && num != 100: Console.WriteLine("Combined case"); break; // The default case can be written as: case var _: Console.WriteLine("Not expected value of obj"); break; } } |
And traditionally, let’s look at the decompiled version:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 | void Demo(object obj) { object obj1 = obj; if (obj1 != null) { int? nullable1 = obj1 as int?; int valueOrDefault1 = nullable1.GetValueOrDefault(); if (!nullable1.HasValue || valueOrDefault1 != 10) { switch (obj1 as string) { case "Hello World": Console.WriteLine("string const"); break; default: if (!(obj1 is Cat)) { string str1; if ((str1 = obj1 as string) != null) goto label_11; label_5: long? nullable2 = obj1 as long?; long valueOrDefault2 = nullable2.GetValueOrDefault(); if (nullable2.HasValue) goto label_13; label_6: string s; int result; if ((s = obj1 as string) != null && int.TryParse(s, out result) && result != 100) { Console.WriteLine("Combined case"); break; } Console.WriteLine("Not expected value of obj"); break; label_13: long num = valueOrDefault2; if (num > 0L && num < 1000L) { Console.WriteLine(num); break; } goto label_6; label_11: string str2 = str1; if (str2.Length > 10 && str2 != "Hello World") { Console.WriteLine(str2); break; } goto label_5; } else { Console.WriteLine("Argument is Cat"); break; } } } else Console.WriteLine("int const"); } else Console.WriteLine("Argument is null"); } |
Honestly, I don’t even want to try to understand what is happening there…
As you can see, pattern matching and the new syntax related to it help simplify life very much and make the code much cleaner. There are rumors that all this stuff will be even more extended in the next language versions. And now, try new stuff in your projects and may the force be with you!
15 years ago Microsoft presented its own vision of programming language. The name "C sharp" was inspired by musical notation where a sharp indicates that the written note should be made a semitone higher in pitch. Last year Microsoft presented new features in C# 6.0. Their goal was to simplify coding…
Task mechanism in C# is a powerful beast in the area of parallel and asynchrony programming. Controlling this beast may take lots of efforts and pain. .NET Framework 4 introduces a convenient approach for cancellation of asynchronous operations. How do we control Why should we control execution flow of the tasks?…
Even though async/await mechanism lets you do complicated things easier, it is still the complicated subject by itself. This article sheds some light on the features and possible pitfalls that you may encounter writing async methods. Async method signature can have three types of the return value: void, Task and Task<T>.…