If statement execution flow in C Sharp (C#) - Time & Space Complexity

Time Complexity: If statement execution flow

O(1)

Understanding Time Complexity

We want to understand how the time it takes to run an if statement changes as the input changes.

Specifically, we ask: does the if statement make the program slower when inputs grow?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int CheckNumber(int n)
{
    if (n > 0)
    {
        return 1;
    }
    else
    {
        return -1;
    }
}
    

This code checks if a number is positive and returns 1 or -1 accordingly.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: A single if condition check.
• How many times: Exactly once per function call.

How Execution Grows With Input

Whether the input number is small or large, the if statement runs just once.

Input Size (n)	Approx. Operations
10	1 check
100	1 check
1000	1 check

Pattern observation: The number of operations stays the same no matter how big the input is.

Final Time Complexity

Time Complexity: O(1)

This means the if statement takes the same amount of time no matter the input size.

Common Mistake

[X] Wrong: "If statements take longer when numbers are bigger because they compare values."

[OK] Correct: The if condition runs once and does not repeat, so size of the number does not affect time.

Interview Connect

Understanding that simple if checks run in constant time helps you explain how decisions in code affect performance.

Self-Check

"What if we added a loop that runs n times inside the if block? How would the time complexity change?"

Practice

1. What does an if statement do in C#?

easy

A. It defines a new variable.

B. It repeats code multiple times.

C. It chooses which code to run based on a condition.

D. It stops the program immediately.

Solution

1. Step 1: Understand the purpose of if

   An if statement checks a condition to decide which code runs next.

2. Step 2: Compare options

   Only It chooses which code to run based on a condition. describes choosing code based on a condition, which matches the if statement's role.

3. Final Answer:

   It chooses which code to run based on a condition. -> Option C

4. Quick Check:

   if chooses code path = C [OK]

Hint: If checks true/false to pick code path quickly [OK]

Common Mistakes:

• Confusing if with loops
• Thinking if defines variables
• Believing if stops program

2. Which of these is the correct syntax for an if statement in C#?

easy

A. if (x > 5) Console.WriteLine("Yes") end

B. if x > 5 then Console.WriteLine("Yes")

C. if x > 5: Console.WriteLine("Yes")

D. if (x > 5) { Console.WriteLine("Yes"); }

Solution

1. Step 1: Review C# if syntax

   C# requires parentheses around the condition and braces for the block.

2. Step 2: Check each option

   if (x > 5) { Console.WriteLine("Yes"); } uses parentheses and braces correctly; others use wrong keywords or punctuation.

3. Final Answer:

   if (x > 5) { Console.WriteLine("Yes"); } -> Option D

4. Quick Check:

   Correct C# if syntax = D [OK]

Hint: Remember: if(condition) { code } in C# [OK]

Common Mistakes:

• Omitting parentheses around condition
• Using Python or other language syntax
• Missing braces for code block

3. What will this code print?

int x = 10;
if (x < 5) {
  Console.WriteLine("Less");
} else {
  Console.WriteLine("More or equal");
}

medium

A. Less

B. More or equal

C. Nothing

D. Error

Solution

1. Step 1: Evaluate the condition

   The condition x < 5 is false because x is 10.

2. Step 2: Determine which block runs

   Since the condition is false, the else block runs, printing "More or equal".

3. Final Answer:

   More or equal -> Option B

4. Quick Check:

   Condition false -> else runs = A [OK]

Hint: If false, else block runs [OK]

Common Mistakes:

• Thinking if block runs when false
• Ignoring else block
• Confusing < with >

4. Find the error in this code:

int num = 7;
if num > 5 {
  Console.WriteLine("Big");
} else {
  Console.WriteLine("Small");
}

medium

A. Missing parentheses around the condition

B. Missing semicolon after if

C. Wrong keyword else

D. Variable num not declared

Solution

1. Step 1: Check if statement syntax

   C# requires parentheses around the condition in an if statement.

2. Step 2: Identify the error

   The code has if num > 5 { without parentheses, causing a syntax error.

3. Final Answer:

   Missing parentheses around the condition -> Option A

4. Quick Check:

   Parentheses needed in if condition = A [OK]

Hint: Always put condition inside parentheses in if [OK]

Common Mistakes:

• Forgetting parentheses in if
• Adding semicolon after if line
• Misusing else keyword

5. You want to print "Positive", "Negative", or "Zero" based on an integer n. Which code correctly uses if statements to do this?

hard

A. if (n > 0) { Console.WriteLine("Positive"); } else if (n < 0) { Console.WriteLine("Negative"); } else { Console.WriteLine("Zero"); }

B. if (n > 0) Console.WriteLine("Positive"); if (n < 0) Console.WriteLine("Negative"); else Console.WriteLine("Zero");

C. if (n > 0) { Console.WriteLine("Positive"); } else { if (n > 0) { Console.WriteLine("Negative"); } else { Console.WriteLine("Zero"); } }

D. if (n > 0) { Console.WriteLine("Positive"); } else if (n <= 0) { Console.WriteLine("Zero"); } else { Console.WriteLine("Negative"); }

Solution

1. Step 1: Understand the logic needed

   We need to check if n is greater than 0, less than 0, or exactly 0.

2. Step 2: Analyze each option

   if (n > 0) { Console.WriteLine("Positive"); } else if (n < 0) { Console.WriteLine("Negative"); } else { Console.WriteLine("Zero"); } correctly uses if, else if, and else to cover all cases without overlap or missing conditions.

3. Final Answer:

   if (n > 0) { Console.WriteLine("Positive"); } else if (n < 0) { Console.WriteLine("Negative"); } else { Console.WriteLine("Zero"); } -> Option A

4. Quick Check:

   Proper if-else chain covers all cases = B [OK]

Hint: Use if-else if-else chain for multiple conditions [OK]

Common Mistakes:

• Using separate ifs causing multiple prints
• Wrong order of conditions
• Incorrect else condition logic