Skip to main content

These 5 new features in C# 12 - Change your way of coding

C# 12 introduces several exciting new features aimed at improving developer productivity, enhancing language expressiveness, and providing better performance. Below are five new features in C# 12 that stand out:

1. Primary Constructors for Classes

C# 12 brings primary constructors for classes, a feature previously available only for structs. This simplifies the way you declare constructors and initialize class properties.

public class Person(string name, int age)
{
    public string Name { get; } = name;
    public int Age { get; } = age;
}

var person = new Person("John Doe", 30);
Console.WriteLine($"{person.Name}, {person.Age}");

With primary constructors, the parameters are passed directly when creating an instance of the class. This eliminates the need for boilerplate constructor code and reduces redundancy.

2. Collection Expressions

Collection expressions make it easier to work with collections by allowing you to initialize, filter, and manipulate collections more succinctly, without relying on LINQ for every operation.

var numbers = [1, 2, 3, 4, 5];  // New collection initialization syntax
var evens = [n for n in numbers where n % 2 == 0];  // Filtering with collection expression

Console.WriteLine(string.Join(", ", evens));  // Output: 2, 4
This new syntax provides a cleaner, more readable way of constructing and filtering collections, similar to what’s available in languages like Python.

3. Default Lambda Expressions

In C# 12, you can define default lambda expressions, which is helpful when using lambdas as default arguments for parameters. This makes lambdas more flexible and useful in cases where default values are commonly used.

void ProcessNumbers(IEnumerable<int> numbers, Func<int, bool> filter = static x => true)
{
    foreach (var number in numbers)
    {
        if (filter(number))
        {
            Console.WriteLine(number);
        }
    }
}

var numbers = new List<int> { 1, 2, 3, 4, 5 };
ProcessNumbers(numbers, x => x % 2 == 0);  // Filters even numbers
ProcessNumbers(numbers);  // Uses default filter (returns true for all numbers)
This feature provides more power and flexibility when using lambdas, especially in API design.

4. Using Alias for Any Type

In C# 12, the using directive now supports type aliases for any type, not just namespaces. This allows you to create more meaningful and concise names for types, including generic types, which is particularly useful when working with complex types.

using Numbers = System.Collections.Generic.List<int>;

Numbers myNumbers = new() { 1, 2, 3, 4, 5 };
Console.WriteLine(string.Join(", ", myNumbers));  // Output: 1, 2, 3, 4, 5
This feature enhances code readability and makes it easier to work with long or complex type names.

5. Improved constexpr (Constant Expressions)

C# 12 enhances constant expressions, allowing more expressions to be evaluated at compile time. This includes some types of method calls, making it possible to compute values at compile time that were previously only computable at runtime.

public class MathConstants
{
    public const double Pi = Math.PI;  // Pi is computed as a constant expression
    public const double Circumference(double radius) => 2 * Pi * radius;  // Compile-time constant expression
}

Console.WriteLine(MathConstants.Circumference(5));  // Output: 31.41592653589793
This improvement can significantly optimize performance by reducing runtime computation and enhancing compile-time validation.

Conclusion

C# 12 adds significant features that improve the overall developer experience. These five features — Primary Constructors, Collection Expressions, Default Lambdas, Type Aliases, and Improved Constant Expressions — make C# more powerful, expressive, and easier to work with in modern applications. These changes demonstrate the language’s continuing evolution, ensuring that C# remains one of the most productive and flexible programming languages available.

Comments

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

How Does My .NET Core Application Build Once and Run Everywhere?

One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...

Clean Architecture: What It Is and How It Differs from Microservices

In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...