Skip to main content

C# : Most used unknown Keywords

C# is a rich and versatile language with many features that make it a favourite among developers. 

While popular keywords like class, if, and foreach are well-known, there are some lesser-known yet powerful keywords that play a crucial role in specific scenarios.

 In this blog post, we'll unravel the mysteries behind these keywords with enlightening code snippets.

yield - Lazy Iteration

public IEnumerable<int> GenerateNumbers()
{
    for (int i = 0; i < 5; i++)
    {
        yield return i;
    }
}

// Usage
foreach (var number in GenerateNumbers())
{
    Console.WriteLine(number);
}

The yield keyword allows the creation of iterators in a more memory-efficient and lazy way. It's particularly useful when generating a sequence of values on-the-fly.

using - Resource Management

using (var resource = new MyDisposableResource())
{
    // Code that uses the resource
}

While using is a common keyword for handling disposable resources, its power is often overlooked. It ensures that the Dispose method of the resource is called, even if an exception is thrown within the block.

nameof - Compile-Time Safety

string propertyName = nameof(MyClass.MyProperty);

The nameof operator provides a way to get the name of a variable, type, or member at compile-time. This helps in avoiding magic strings, making code more maintainable.

async and await - Asynchronous Programming

async Task<string> FetchDataAsync()
{
    var result = await HttpClient.GetAsync("https://example.com/api/data");
    return await result.Content.ReadAsStringAsync();
}

The async and await keywords facilitate asynchronous programming, allowing the creation of responsive applications without blocking the main thread.

params - Variable Number of Arguments

void DisplayNumbers(params int[] numbers)
{
    foreach (var number in numbers)
    {
        Console.WriteLine(number);
    }
}

// Usage
DisplayNumbers(1, 2, 3, 4, 5);

The params keyword enables methods to accept a variable number of arguments of the specified type.

readonly - Immutable Fields

public class Constants
{
    public readonly int MaxValue = 100;
}

The readonly keyword ensures that a field can only be assigned a value at the time of declaration or in the constructor, making it immutable.

unsafe - Unsafe Code

unsafe void Square(int* number)
{
    *number = *number * *number;
}

// Usage
int value = 5;
Square(&value);

The unsafe keyword allows the use of pointers, enabling low-level operations. It should be used with caution due to potential security risks.

default - Default Values

int defaultInt = default;        // 0
bool defaultBool = default;      // false
string defaultString = default;  // null

The default keyword provides the default value for a given type, making code more concise and readable.

Conclusion

These lesser-known keywords might not be in the spotlight, but they play significant roles in specific scenarios, offering unique capabilities that contribute to the overall richness of the C# language.

 By exploring and understanding these keywords, developers can enhance their coding skills and make more informed design decisions. Happy coding!

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...

.NET 10: Your Ultimate Guide to the Coolest New Features (with Real-World Goodies!)

 Hey .NET warriors! 🤓 Are you ready to explore the latest and greatest features that .NET 10 and C# 14 bring to the table? Whether you're a seasoned developer or just starting out, this guide will show you how .NET 10 makes your apps faster, safer, and more productive — with real-world examples to boot! So grab your coffee ☕️ and let’s dive into the awesome . 💪 1️⃣ JIT Compiler Superpowers — Lightning-Fast Apps .NET 10 is all about speed . The Just-In-Time (JIT) compiler has been turbocharged with: Stack Allocation for Small Arrays 🗂️ Think fewer heap allocations, less garbage collection, and blazing-fast performance . Better Code Layout 🔥 Hot code paths are now smarter, meaning faster method calls and fewer CPU cache misses. 💡 Why you care: Your APIs, desktop apps, and services now respond quicker — giving users a snappy experience . 2️⃣ Say Hello to C# 14 — More Power in Your Syntax .NET 10 ships with C# 14 , and it’s packed with developer goodies: Field-Bac...

Optional Parameters in C# — Writing Flexible and Clean Methods

Hello, .NET developers! 👋 How often have you created multiple method overloads just to handle slightly different cases? Maybe one method accepts two parameters, another three, and one more adds a flag for debugging? That’s a lot of code duplication for something that can be solved beautifully with optional parameters . Optional parameters in C# let you define default values for method arguments. When a caller doesn’t pass a value, the compiler automatically substitutes the default. This feature helps keep your APIs simple, readable, and maintainable. 🎥 Explore more on YouTube : DotNet Full Stack Dev Understanding Optional Parameters Optional parameters are defined by assigning default values in the method signature. When calling the method, you can omit those parameters if you’re okay with the defaults. Example public class Logger { public void Log(string message, string level = "INFO", bool writeToFile = false) ...