Why LINQ depends on extension methods in C Sharp (C#) - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this LINQ extension method call?

Consider the following C# code using LINQ extension methods. What will be printed to the console?

C Sharp (C#)

using System;
using System.Linq;

class Program {
    static void Main() {
        int[] numbers = {1, 2, 3, 4, 5};
        var evens = numbers.Where(n => n % 2 == 0);
        foreach(var num in evens) {
            Console.Write(num + " ");
        }
    }
}

A Compilation error

B 1 2 3 4 5

C 1 3 5

D 2 4

💡 Hint

Remember that Where filters elements based on the condition.

The Where extension method filters the array to include only even numbers (n % 2 == 0). So only 2 and 4 are printed.

🧠 Conceptual

intermediate

Why does LINQ use extension methods?

Why does LINQ rely on extension methods in C#?

A Because extension methods allow adding new methods to existing types without modifying them.

B Because extension methods improve runtime performance significantly.

C Because extension methods are the only way to create static methods in C#.

D Because extension methods automatically generate SQL queries.

💡 Hint

Think about how LINQ adds query capabilities to collections.

Extension methods let LINQ add query methods like Where and Select to existing types like IEnumerable without changing their source code.

🔧 Debug

advanced

What error does this LINQ extension method code produce?

Examine the code below. What error will occur when compiling or running it?

C Sharp (C#)

using System;
using System.Linq;

class Program {
    static void Main() {
        int[] numbers = null;
        var result = numbers.Where(n => n > 0);
        Console.WriteLine(result.Count());
    }
}

A ArgumentNullException at runtime

B Compilation error: 'Where' method not found

C Output: 0

D InvalidOperationException at runtime

💡 Hint

What happens when you call a LINQ extension method with a null source?

Calling Where on a null IEnumerable causes an ArgumentNullException at runtime because LINQ validates that the source is not null.

📝 Syntax

advanced

Which option correctly defines a LINQ extension method?

Which of the following is a correct way to define a LINQ-style extension method for IEnumerable?

C Sharp (C#)

using System.Collections.Generic;

A public static IEnumerable<T> Filter<T>(IEnumerable<T> source, Func<T, bool> predicate) { foreach(var item in source) if(predicate(item)) yield return item; }

B public IEnumerable<T> Filter<T>(IEnumerable<T> source, Func<T, bool> predicate) { foreach(var item in source) if(predicate(item)) yield return item; }

C public static IEnumerable<T> Filter<T>(this IEnumerable<T> source, Func<T, bool> predicate) { foreach(var item in source) if(predicate(item)) yield return item; }

D public static IEnumerable<T> Filter<T>(this IEnumerable<T> source, bool predicate(T item)) { foreach(var item in source) if(predicate(item)) yield return item; }

💡 Hint

Extension methods must be static and have 'this' before the first parameter.

Option C correctly defines a static extension method with 'this' keyword on the first parameter and uses Func delegate.

🚀 Application

expert

How does LINQ's use of extension methods enable query chaining?

LINQ methods like Where and Select can be chained together fluently. How does the use of extension methods enable this chaining?

A Because extension methods modify the original collection in place to add query results.

B Because each extension method returns an IEnumerable<T>, allowing the next method to be called on the result.

C Because extension methods compile queries into SQL automatically for chaining.

D Because extension methods use reflection to dynamically add methods at runtime.

💡 Hint

Think about what each LINQ method returns and how that allows calling another method.

Each LINQ extension method returns an IEnumerable representing the filtered or transformed sequence, so you can call another LINQ method on it, enabling chaining.