Menu

How to Use is and as Keywords for Type Checking in C#

Type checking and conversion are essential operations in C#'s object-oriented programming model.

The is and as keywords provide elegant solutions for safely working with types at runtime. Understanding when and how to use each can significantly improve your code's robustness and readability.

The is Operator: Type Checking

The is operator evaluates whether an object is compatible with a given type, returning a boolean result.

Basic Usage

object value = "Hello, World!";

// Check if value is a string
if (value is string)
{
    Console.WriteLine("value is a string");
}

Pattern Matching (C# 7.0+)

// Type checking with declaration
if (value is string message)
{
    // message is now a string variable containing the value
    Console.WriteLine($"Length: {message.Length}");
}

Type Patterns with Conditions (C# 9.0+)

// Check type and condition in one step
if (value is string { Length: > 5 } longString)
{
    Console.WriteLine($"Long string found: {longString}");
}

The as Operator: Safe Casting

The as operator attempts to cast an object to a specified reference type, returning null if the cast fails rather than throwing an exception.

Basic Usage

object value = "Hello, World!";

// Try to cast to string
string message = value as string;

// Check if cast was successful
if (message != null)
{
    Console.WriteLine($"Successful cast: {message}");
}

Important Limitations

  • The as operator only works with reference types and nullable value types
  • It cannot be used with non-nullable value types (use is with pattern matching instead)

Choosing Between is and as

Scenario Recommended Approach
Just checking type Use is
Checking type and using the object Use is with pattern matching
Possibly working with a null result Use as
Working with value types Use is (with pattern matching if needed)
Multiple operations on same cast Use as once, then check for null

Best Practices

  1. Prefer pattern matching with is when you need both type checking and casting
  2. Use as when working with hierarchies where null is a valid outcome
  3. Avoid as followed by null checking when is pattern matching works
  4. Remember that as never throws exceptions, while direct casting can
  5. Consider extension methods as an alternative to frequent type checking

Understanding these operators helps you write more elegant, safe code when working with polymorphic types in C#.

0
50

Related

Removing duplicates from a list in C# is a common task, especially when working with large datasets. C# provides multiple ways to achieve this efficiently, leveraging built-in collections and LINQ.

Using HashSet (Fastest for Unique Elements)

A HashSet<T> automatically removes duplicates since it only stores unique values. This is one of the fastest methods:

List<int> numbers = new List<int> { 1, 2, 2, 3, 4, 4, 5 };
numbers = new HashSet<int>(numbers).ToList();
Console.WriteLine(string.Join(", ", numbers)); // Output: 1, 2, 3, 4, 5

Using LINQ Distinct (Concise and Readable)

LINQ’s Distinct() method provides an elegant way to remove duplicates:

List<int> numbers = new List<int> { 1, 2, 2, 3, 4, 4, 5 };
numbers = numbers.Distinct().ToList();
Console.WriteLine(string.Join(", ", numbers)); // Output: 1, 2, 3, 4, 5

Removing Duplicates by Custom Property (For Complex Objects)

When working with objects, DistinctBy() from .NET 6+ simplifies duplicate removal based on a property:

using System.Linq;
using System.Collections.Generic;

class Person
{
    public string Name { get; set; }
    public int Age { get; set; }
}

List<Person> people = new List<Person>
{
    new Person { Name = "Alice", Age = 30 },
    new Person { Name = "Bob", Age = 25 },
    new Person { Name = "Alice", Age = 30 }
};

people = people.DistinctBy(p => p.Name).ToList();
Console.WriteLine(string.Join(", ", people.Select(p => p.Name))); // Output: Alice, Bob

For earlier .NET versions, use GroupBy():

people = people.GroupBy(p => p.Name).Select(g => g.First()).ToList();

Performance Considerations

  • HashSet<T> is the fastest but only works for simple types.
  • Distinct() is easy to use but slower than HashSet<T> for large lists.
  • DistinctBy() (or GroupBy()) is useful for complex objects but may have performance trade-offs.

Conclusion

Choosing the best approach depends on the data type and use case. HashSet<T> is ideal for primitive types, Distinct() is simple and readable, and DistinctBy() (or GroupBy()) is effective for objects.

1
442

When working with SQL Server, you may often need to count the number of unique values in a specific column. This is useful for analyzing data, detecting duplicates, and understanding dataset distributions.

Using COUNT(DISTINCT column_name)

To count the number of unique values in a column, SQL Server provides the COUNT(DISTINCT column_name) function. Here’s a simple example:

SELECT COUNT(DISTINCT column_name) AS distinct_count
FROM table_name;

This query will return the number of unique values in column_name.

Counting Distinct Values Across Multiple Columns

If you need to count distinct combinations of multiple columns, you can use a subquery:

SELECT COUNT(*) AS distinct_count
FROM (SELECT DISTINCT column1, column2 FROM table_name) AS subquery;

This approach ensures that only unique pairs of column1 and column2 are counted.

Why Use COUNT DISTINCT?

  • Helps in identifying unique entries in a dataset.
  • Useful for reporting and analytics.
  • Efficient way to check for duplicates.

By leveraging COUNT(DISTINCT column_name), you can efficiently analyze your database and extract meaningful insights. Happy querying!

1
120

Reading a file line by line is useful when handling large files without loading everything into memory at once.

✅ Best Practice: Use File.ReadLines() which is more memory efficient.

Example

foreach (string line in File.ReadLines("file.txt"))
{
    Console.WriteLine(line);
}

Why use ReadLines()?

Reads one line at a time, reducing overall memory usage. Ideal for large files (e.g., logs, CSVs).

Alternative: Use StreamReader (More Control)

For scenarios where you need custom processing while reading the contents of the file:

using (StreamReader reader = new StreamReader("file.txt"))
{
    string? line;
    while ((line = reader.ReadLine()) != null)
    {
        Console.WriteLine(line);
    }
}

Why use StreamReader?

Lets you handle exceptions, encoding, and buffering. Supports custom processing (e.g., search for a keyword while reading).

When to Use ReadAllLines()? If you need all lines at once, use:

string[] lines = File.ReadAllLines("file.txt");

Caution: Loads the entire file into memory—avoid for large files!

4
319