Methods that operate on state in C Sharp (C#) - Time & Space Complexity

Time Complexity: Methods that operate on state

O(1)

Understanding Time Complexity

When methods change or use stored information, it affects how long the program takes to run.

We want to know how the time grows when these methods work on bigger or more data.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Counter
{
    private int count = 0;

    public void Increment()
    {
        count++;
    }

    public int GetCount()
    {
        return count;
    }
}

This code defines a class with a number that can be increased and read.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Single increment or return of a stored number.
• How many times: Each method runs once per call, no loops inside.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	10 increments or reads
100	100 increments or reads
1000	1000 increments or reads

Pattern observation: Each call does a fixed small task, so time grows directly with how many times you call the method.

Final Time Complexity

Time Complexity: O(1)

This means each method call takes the same small amount of time, no matter how big the data or how many times it was called before.

Common Mistake

[X] Wrong: "Incrementing a stored number takes longer as the number gets bigger."

[OK] Correct: The method just adds one to a number, which is a simple step and does not get slower with bigger numbers.

Interview Connect

Understanding how simple methods that change or read stored data work helps you explain and write efficient code in real projects.

Self-Check

"What if the Increment method added a loop that counted up to the current number? How would the time complexity change?"

Practice

1. What is the main purpose of methods that operate on state in a C# class?

easy

A. To perform calculations without changing any data

B. To allow objects to keep and change their own data safely

C. To handle user input from the console

D. To create new classes from existing ones

Solution

1. Step 1: Understand what 'state' means in programming

   State refers to the data stored inside an object that can change over time.

2. Step 2: Identify the role of methods operating on state

   These methods allow the object to update or read its own data safely, keeping control inside the object.

3. Final Answer:

   To allow objects to keep and change their own data safely -> Option B

4. Quick Check:

   Methods on state = safe data change inside object [OK]

Hint: Think: methods change or read object's own data [OK]

Common Mistakes:

• Confusing methods on state with inheritance
• Thinking methods only perform calculations
• Believing methods handle external input only

2. Which of the following is the correct syntax for a method that changes an object's state in C#?

easy

A. public void UpdateName(string newName) { name = newName; }

B. void UpdateName(string newName) name = newName;

C. public UpdateName(string newName) { name = newName; }

D. public void UpdateName(string newName) => return name = newName;

Solution

1. Step 1: Check method declaration syntax

   In C#, methods must specify access modifier, return type, name, and parameters inside parentheses, with body in braces.

2. Step 2: Verify the method body updates the state correctly

   public void UpdateName(string newName) { name = newName; } correctly assigns newName to the field name inside braces.

3. Final Answer:

   public void UpdateName(string newName) { name = newName; } -> Option A

4. Quick Check:

   Correct method syntax = public void UpdateName(string newName) { name = newName; } [OK]

Hint: Remember method syntax: access + return type + name(params) { body } [OK]

Common Mistakes:

• Missing braces around method body
• Omitting return type
• Using return with void methods incorrectly

3. What will be the output of this C# code?

class Counter {
  private int count = 0;
  public void Increment() { count++; }
  public int GetCount() { return count; }
}

var c = new Counter();
c.Increment();
c.Increment();
Console.WriteLine(c.GetCount());

medium

A. 3

B. 1

C. 0

D. 2

Solution

1. Step 1: Trace the Increment method calls

   Each call to Increment increases count by 1. Two calls increase count from 0 to 2.

2. Step 2: Check the GetCount method output

   GetCount returns the current count, which is 2 after two increments.

3. Final Answer:

   2 -> Option D

4. Quick Check:

   2 increments = count 2 [OK]

Hint: Count increments twice, so output is 2 [OK]

Common Mistakes:

• Forgetting that count starts at 0
• Assuming Increment adds more than 1
• Confusing method names or outputs

4. Identify the error in this method that tries to update an object's state:

public void SetAge(int age) {
  int age = age;
}

medium

A. The method redeclares 'age' variable causing a conflict

B. The method is missing a return statement

C. The method should be static to update state

D. The method should not have parameters

Solution

1. Step 1: Analyze variable declarations inside the method

   The method declares a new local variable 'int age', which conflicts with the parameter 'age'.

2. Step 2: Understand how to update the object's field

   To update the object's state, assign the parameter to the field, e.g., this.age = age; without redeclaring.

3. Final Answer:

   The method redeclares 'age' variable causing a conflict -> Option A

4. Quick Check:

   Variable redeclaration error = The method redeclares 'age' variable causing a conflict [OK]

Hint: Don't redeclare parameter names inside method [OK]

Common Mistakes:

• Thinking missing return causes error in void method
• Assuming static needed to update instance state
• Believing parameters should be removed

5. You have a class BankAccount with a private field balance. You want to add a method Withdraw that subtracts an amount only if there is enough balance. Which method implementation correctly operates on the state safely?

hard

A. public decimal Withdraw(decimal amount) { return balance - amount; }

B. public void Withdraw(decimal amount) { balance -= amount; }

C. public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); }

D. public void Withdraw(decimal amount) { if (amount < 0) balance += amount; }

Solution

1. Step 1: Check for safe state update conditions

   Method should only subtract amount if balance is enough to avoid negative balance.

2. Step 2: Verify method behavior on insufficient funds

   public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } checks amount <= balance and prints a message if not enough, preventing invalid state.

3. Final Answer:

   public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } -> Option C

4. Quick Check:

   Safe state update with condition = public void Withdraw(decimal amount) { if (amount <= balance) balance -= amount; else Console.WriteLine("Insufficient funds"); } [OK]

Hint: Check balance before subtracting to avoid negative state [OK]

Common Mistakes:

• Subtracting without checking balance
• Returning new value without updating state
• Adding amount when negative instead of subtracting