Pattern matching, which was introduced in C# 9, is a hell of a beast and does more than you might think.
In this small blog post I show you where the magic is and what it does under the hood.

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

Pattern matching, introduced in C# 9, is a hell of a beast and does more than you might think. In the code below you see two times the same signature but the outcome is different. So it is save to pass in null without getting any NullPointerException.

Pattern matching is awesome

I love pattern matching. Almost everything new I implement has it in large quantities.
Pattern matching &amp; Switch Expressions are like 40% of my code (hyperbole)
<pre><code class="language-csharp">return person switch 
{
 {FirstName: null or &quot;&quot;} =&gt; Fail(&quot;No first name&quot;),
 _ when person.FirstName == &quot;Invalid&quot;=&gt; Fail(&quot;First name is invalid&quot;),
_ =&gt; Ok(&quot;Person has a valid firstname&quot;),
};
</code></pre>