First, Single, and their OrDefault variants in C Sharp (C#) - Step-by-Step Execution

Concept Flow - First, Single, and their OrDefault variants

Start with a collection

↓

Check if collection is empty?

↓

Return default

↓

Throw exception

This flow shows how First and Single methods check the collection: if empty, return default or throw; if multiple matches for Single, throw; otherwise return the element.

Execution Sample

C Sharp (C#)

var numbers = new[] {1, 2, 3};
var first = numbers.First();
var single = numbers.Single(x => x == 2);
var firstOrDefault = numbers.FirstOrDefault(x => x > 3);
var singleOrDefault = numbers.SingleOrDefault(x => x > 3);

This code gets the first element, a single matching element, and uses OrDefault variants to safely handle no matches.

Execution Table

Step	Method Call	Condition Checked	Result	Action Taken
1	First()	Collection not empty	True	Return first element: 1
2	Single(x == 2)	Exactly one element matches	True	Return element: 2
3	FirstOrDefault(x > 3)	Any element matches?	False	Return default: 0
4	SingleOrDefault(x > 3)	Any element matches?	False	Return default: 0
5	Single(x > 1)	More than one element matches	True	Throw InvalidOperationException
6	First()	Collection empty	False	Throw InvalidOperationException
7	FirstOrDefault()	Collection empty	True	Return default: 0

💡 Execution stops when method returns element, default, or throws exception.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
numbers	[1, 2, 3]	[1, 2, 3]	[1, 2, 3]	[1, 2, 3]	[1, 2, 3]
first	undefined	1	1	1	1
single	undefined	undefined	2	2	2
firstOrDefault	undefined	undefined	undefined	0	0
singleOrDefault	undefined	undefined	undefined	undefined	0

Key Moments - 3 Insights

Why does Single throw an exception when more than one element matches?

Single expects exactly one match. If multiple elements match, it throws to signal ambiguity, as shown in step 5 of the execution_table.

What is the difference between First and FirstOrDefault when the collection is empty?

First throws an exception if empty (step 6), while FirstOrDefault returns the default value (step 7), avoiding exceptions.

When does SingleOrDefault return default instead of throwing?

SingleOrDefault returns default if no elements match (step 4), but throws if multiple elements match, unlike FirstOrDefault.

Visual Quiz - 3 Questions

Look at the execution_table, what value does 'firstOrDefault' have after step 3?

A 2

B 0

C 1

D Exception thrown

💡 Hint

Check the 'Result' and 'Action Taken' columns for step 3 in execution_table.

At which step does Single throw an exception due to multiple matches?

A Step 5

B Step 2

C Step 6

D Step 7

💡 Hint

Look for 'Throw InvalidOperationException' in the 'Action Taken' column.

If the collection was empty, what would First() do according to the execution_table?

A Return default value

B Return first element

C Throw InvalidOperationException

D Return null

💡 Hint

See step 6 where First() is called on an empty collection.

Concept Snapshot

First() returns the first element or throws if empty.
Single() returns the only matching element or throws if none or multiple.
FirstOrDefault() returns first element or default if empty.
SingleOrDefault() returns single matching element or default if none, throws if multiple.
Use OrDefault variants to avoid exceptions on empty or no matches.

Full Transcript

This visual execution shows how First, Single, and their OrDefault variants work in C#. First returns the first element or throws if the collection is empty. Single returns the only matching element or throws if none or more than one match exists. The OrDefault variants return default values instead of throwing exceptions when no elements match or the collection is empty. The execution table traces each method call, conditions checked, and results or exceptions. Variable tracking shows how variables change after each step. Key moments clarify common confusions about exceptions and default returns. The quiz tests understanding of method behaviors at specific steps.