When clause in catch in C Sharp (C#) - Time & Space Complexity

Time Complexity: When clause in catch

O(n)

Understanding Time Complexity

We want to understand how using a when clause in a catch block affects the time it takes for a program to handle errors.

Specifically, we ask: does adding a when condition change how long the program runs as input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

try
{
    for (int i = 0; i < n; i++)
    {
        ProcessItem(i);
    }
}
catch (Exception ex) when (ex.Message.Contains("specific"))
{
    HandleSpecificError();
}
catch (Exception ex)
{
    HandleGeneralError();
}
    

This code processes n items in a loop and uses a when clause to catch exceptions with a specific message.

Identify Repeating Operations

• Primary operation: The for loop that runs ProcessItem(i) n times.
• How many times: Exactly n times, once for each item.
• Exception check: The when clause runs only if an exception occurs, checking the message condition.

How Execution Grows With Input

As n grows, the loop runs more times, so the main work grows with n.

Input Size (n)	Approx. Operations
10	About 10 calls to ProcessItem
100	About 100 calls to ProcessItem
1000	About 1000 calls to ProcessItem

Pattern observation: The main work grows directly with n. The when clause only runs if an exception happens, so it does not add repeated cost for normal runs.

Final Time Complexity

Time Complexity: O(n)

This means the program's running time grows in a straight line with the number of items processed, regardless of the when clause.

Common Mistake

[X] Wrong: "Adding a when clause makes the whole loop slower because it checks the condition every time."

[OK] Correct: The when clause only runs when an exception is thrown, which is usually rare. It does not slow down the normal loop iterations.

Interview Connect

Understanding how exception handling affects performance shows you can write clear and efficient error management. This skill helps you build reliable programs that handle problems without slowing down normal work.

Self-Check

What if the when clause checked a complex condition that runs every loop iteration instead of only on exceptions? How would the time complexity change?

Practice

1.

What does the when clause do in a catch block in C#?

easy

A. It adds a condition to run the catch block only if the condition is true.

B. It defines a new exception type to catch.

C. It skips the catch block entirely.

D. It makes the catch block run before the try block.

Solution

1. Step 1: Understand the purpose of the when clause

   The when clause adds a condition to a catch block.

2. Step 2: Effect of the when clause in exception handling

   The catch block runs only if the condition after when is true, otherwise it skips.

3. Final Answer:

   It adds a condition to run the catch block only if the condition is true. -> Option A

4. Quick Check:

   when clause = conditional catch [OK]

Hint: when clause filters catch by condition [OK]

Common Mistakes:

• Thinking when defines a new exception type
• Assuming catch runs always regardless of when
• Confusing when with finally block

2.

Which of the following is the correct syntax to use a when clause in a catch block?

try {
    // code
} catch (Exception ex) _____ {
    // handle
}

easy

A. while (ex.Message.Contains("error"))

B. if (ex.Message.Contains("error"))

C. where (ex.Message.Contains("error"))

D. when (ex.Message.Contains("error"))

Solution

1. Step 1: Recall the correct keyword for condition in catch

   The correct keyword to add a condition in catch is when.

2. Step 2: Match the syntax with the options

   Only when (ex.Message.Contains("error")) uses when correctly with the condition.

3. Final Answer:

   when (ex.Message.Contains("error")) -> Option D

4. Quick Check:

   Use 'when' keyword for catch condition [OK]

Hint: Use 'when' keyword, not if/where/while in catch [OK]

Common Mistakes:

• Using if instead of when in catch
• Confusing when with where or while
• Missing parentheses after when

3.

What will be the output of this code?

try {
    throw new InvalidOperationException("Invalid operation");
} catch (InvalidOperationException ex) when (ex.Message.Contains("Invalid")) {
    Console.WriteLine("Caught invalid operation");
} catch (Exception) {
    Console.WriteLine("Caught general exception");
}

medium

A. Caught general exception

B. Caught invalid operation

C. No output

D. Runtime error

Solution

1. Step 1: Identify the thrown exception and matching catch

   The code throws InvalidOperationException with message containing "Invalid".

2. Step 2: Check the when condition in the first catch

   The first catch has a when clause checking if message contains "Invalid" which is true, so it runs.

3. Final Answer:

   Caught invalid operation -> Option B

4. Quick Check:

   when condition true runs first catch [OK]

Hint: Check exception type and when condition carefully [OK]

Common Mistakes:

• Ignoring the when condition and picking second catch
• Assuming no output if when is used
• Confusing exception types

4.

Find the error in this code snippet:

try {
    // some code
} catch (Exception ex) when ex.Message == "Error" {
    Console.WriteLine("Error caught");
}

medium

A. catch block must not have a condition

B. Cannot use when with Exception type

C. Missing parentheses around the when condition

D. Console.WriteLine is not allowed in catch

Solution

1. Step 1: Check syntax of when clause

   The condition after when must be enclosed in parentheses.

2. Step 2: Identify the missing parentheses in the code

   The code uses when ex.Message == "Error" without parentheses, which is invalid syntax.

3. Final Answer:

   Missing parentheses around the when condition -> Option C

4. Quick Check:

   when condition needs parentheses [OK]

Hint: Always put parentheses after when [OK]

Common Mistakes:

• Omitting parentheses around when condition
• Thinking when can't be used with Exception
• Believing catch can't have code inside

5.

Consider this code:

try {
    throw new ArgumentNullException("param");
} catch (ArgumentNullException ex) when (ex.ParamName == "param") {
    Console.WriteLine("Parameter error");
} catch (ArgumentNullException ex) {
    Console.WriteLine("Other argument null error");
}

What will be printed and why?

hard

A. Parameter error, because the when condition matches the ParamName.

B. Other argument null error, because when clause is ignored.

C. No output, because exception is not caught.

D. Runtime error due to duplicate catch blocks.

Solution

1. Step 1: Identify the thrown exception and its property

   The code throws ArgumentNullException with ParamName set to "param".

2. Step 2: Check the when clause condition in the first catch

   The first catch has a when clause checking if ex.ParamName == "param", which is true, so this catch runs.

3. Step 3: Understand catch block selection

   The second catch is ignored because the first matching catch with true when condition handles the exception.

4. Final Answer:

   Parameter error, because the when condition matches the ParamName. -> Option A

5. Quick Check:

   when true catches first matching block [OK]

Hint: when filters catch; first true condition wins [OK]

Common Mistakes:

• Ignoring when condition and picking second catch
• Thinking duplicate catch causes error
• Assuming exception is uncaught