First, Single, and their OrDefault variants in C Sharp (C#) - Time & Space Complexity

Time Complexity: First, Single, and their OrDefault variants

O(n)

Understanding Time Complexity

When using First, Single, and their OrDefault variants in C#, it's important to know how long these methods take to find an item.

We want to understand how the time to find an element grows as the list gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

var numbers = new List<int> {1, 2, 3, 4, 5};

// Find first even number
int firstEven = numbers.FirstOrDefault(n => n % 2 == 0);

// Find single number equal to 3
int singleThree = numbers.Single(n => n == 3);
    

This code looks for elements matching a condition in a list using FirstOrDefault and Single.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each element one by one until a match is found.
• How many times: Up to all elements in the list in the worst case.

How Execution Grows With Input

As the list grows, the time to find the element grows roughly in direct proportion.

Input Size (n)	Approx. Operations
10	Up to 10 checks
100	Up to 100 checks
1000	Up to 1000 checks

Pattern observation: The number of checks grows linearly with the list size.

Final Time Complexity

Time Complexity: O(n)

This means the time to find the element grows in a straight line as the list gets bigger.

Common Mistake

[X] Wrong: "First or Single methods instantly find the element regardless of list size."

[OK] Correct: These methods check elements one by one until they find a match, so bigger lists take more time.

Interview Connect

Understanding how these methods work helps you explain your code choices clearly and shows you know what happens behind the scenes.

Self-Check

"What if the list was sorted and you used a method that stops searching early? How would the time complexity change?"

Practice

1.

Which method will throw an exception if the collection does not have exactly one matching element?

First(), FirstOrDefault(), Single(), SingleOrDefault()

easy

A. SingleOrDefault()

B. First()

C. FirstOrDefault()

D. Single()

Solution

1. Step 1: Understand Single() behavior

   Single() expects exactly one matching element and throws if there are zero or more than one.

2. Step 2: Compare with other methods

   First() and FirstOrDefault() do not throw if multiple elements exist; SingleOrDefault() throws only if multiple elements exist but returns default if none.

3. Final Answer:

   Single() -> Option D

4. Quick Check:

   Throws on multiple matches = Single() [OK]

Hint: Single() throws if more than one match exists [OK]

Common Mistakes:

• Confusing Single() with First() which returns first match
• Thinking FirstOrDefault() throws on multiple matches
• Assuming SingleOrDefault() never throws

2.

Which of the following is the correct syntax to get the first element or default from a list numbers?

var result = numbers._____();

easy

A. Single

B. FirstOrDefault

C. First

D. SingleOrDefault

Solution

1. Step 1: Identify method for first or default

   FirstOrDefault() returns the first element or default if none found.

2. Step 2: Check syntax correctness

   numbers.FirstOrDefault() is valid syntax to get first or default.

3. Final Answer:

   FirstOrDefault -> Option B

4. Quick Check:

   FirstOrDefault() syntax correct for first or default [OK]

Hint: Use FirstOrDefault() to safely get first or default [OK]

Common Mistakes:

• Using Single() which throws if multiple elements
• Using First() which throws if empty
• Using SingleOrDefault() which expects single element

3.

What will be the output of this code?

var list = new List<int> { 5, 10, 15 };
var result = list.SingleOrDefault(x => x == 10);
Console.WriteLine(result);

medium

A. 10

B. 0

C. Throws exception

D. null

Solution

1. Step 1: Understand SingleOrDefault with predicate

   SingleOrDefault returns the only element matching predicate or default if none, throws if multiple.

2. Step 2: Check list and predicate

   List has one element equal to 10, so SingleOrDefault returns 10.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   SingleOrDefault returns single matching element = 10 [OK]

Hint: SingleOrDefault returns single match or default, throws if many [OK]

Common Mistakes:

• Expecting 0 as default when element exists
• Thinking it throws because of multiple elements in list
• Confusing with FirstOrDefault behavior

4.

Identify the error in this code snippet:

var items = new List<string> { "apple", "banana", "apple" };
var singleItem = items.Single(x => x == "apple");
Console.WriteLine(singleItem);

medium

A. Returns "apple" without error

B. Returns null because of duplicates

C. Throws InvalidOperationException due to multiple matches

D. Syntax error in lambda expression

Solution

1. Step 1: Analyze Single() with multiple matches

   Single() throws InvalidOperationException if more than one element matches the predicate.

2. Step 2: Check list contents

   List has two "apple" strings, so Single() throws exception.

3. Final Answer:

   Throws InvalidOperationException due to multiple matches -> Option C

4. Quick Check:

   Single() throws on multiple matches [OK]

Hint: Single() throws if more than one match found [OK]

Common Mistakes:

• Expecting Single() to return first match
• Thinking it returns null on duplicates
• Assuming syntax error in lambda

5.

You have a list of users and want to get the only user with the username "admin" or null if none exists. Which method should you use to avoid exceptions if there are no or multiple admins?

hard

A. FirstOrDefault()

B. SingleOrDefault() with try-catch

C. Single()

D. First()

Solution

1. Step 1: Understand requirements

   We want the only user named "admin" or null if none, but avoid exceptions if multiple exist.

2. Step 2: Evaluate methods

   SingleOrDefault() throws if multiple matches, so risky. FirstOrDefault() returns first or null safely even if multiple exist.

3. Final Answer:

   FirstOrDefault() -> Option A

4. Quick Check:

   FirstOrDefault() safely returns first or null without exceptions [OK]

Hint: Use FirstOrDefault() to avoid exceptions on multiple matches [OK]

Common Mistakes:

• Using SingleOrDefault() which throws on multiple matches
• Using Single() which throws on zero or multiple matches
• Using First() which throws if none found