Passing reference types to methods in C Sharp (C#) - Time & Space Complexity

Time Complexity: Passing reference types to methods

O(n)

Understanding Time Complexity

When we pass reference types to methods, it's important to know how this affects the program's speed.

We want to see how the time to run changes as the input size grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void UpdateList(List<int> numbers) {
    for (int i = 0; i < numbers.Count; i++) {
        numbers[i] = numbers[i] * 2;
    }
}

List<int> myNumbers = new List<int> {1, 2, 3, 4, 5};
UpdateList(myNumbers);
    

This code doubles each number in a list passed to a method.

Identify Repeating Operations

• Primary operation: Looping through the list to update each element.
• How many times: Once for each item in the list (n times).

How Execution Grows With Input

As the list gets bigger, the method takes longer because it updates every item.

Input Size (n)	Approx. Operations
10	10 updates
100	100 updates
1000	1000 updates

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

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

Common Mistake

[X] Wrong: "Passing a reference type to a method makes the method run instantly regardless of list size."

[OK] Correct: Even though the method gets a reference, it still has to loop through all items, so time grows with list size.

Interview Connect

Understanding how passing reference types affects time helps you explain code efficiency clearly and confidently.

Self-Check

"What if the method only updated the first 5 items regardless of list size? How would the time complexity change?"

Practice

1. What happens when you pass a reference type object to a method in C# without using ref keyword?

easy

A. The method can modify the object's properties, affecting the original object.

B. The method cannot modify the object's properties at all.

C. The method receives a copy of the object and changes do not affect the original.

D. The method can reassign the original reference to a new object automatically.

Solution

1. Step 1: Understand passing reference types

   When a reference type is passed to a method, the method receives a copy of the reference, pointing to the same object.

2. Step 2: Effect on object properties

   Modifying the object's properties inside the method changes the original object because both references point to the same memory.

3. Final Answer:

   The method can modify the object's properties, affecting the original object. -> Option A

4. Quick Check:

   Reference type properties change original [OK]

Hint: Reference types allow property changes to affect original object [OK]

Common Mistakes:

• Thinking the object is copied entirely
• Confusing reference and value types
• Assuming reassignment changes original reference

2. Which of the following method signatures correctly allows a method to reassign a reference type parameter so the caller sees the new object?

easy

A. void UpdateObject(MyClass obj) { obj = new MyClass(); }

B. void UpdateObject(ref MyClass obj) { obj = new MyClass(); }

C. void UpdateObject(out MyClass obj) { obj = new MyClass(); }

D. void UpdateObject(in MyClass obj) { obj = new MyClass(); }

Solution

1. Step 1: Understand parameter passing keywords

   The ref keyword allows the method to reassign the caller's reference variable.

2. Step 2: Analyze each signature

   void UpdateObject(ref MyClass obj) { obj = new MyClass(); } uses ref and assigns a new object, so the caller's reference changes. void UpdateObject(MyClass obj) { obj = new MyClass(); } reassigns local copy only. void UpdateObject(out MyClass obj) { obj = new MyClass(); } requires assignment but is for output parameters. void UpdateObject(in MyClass obj) { obj = new MyClass(); } is readonly and cannot reassign.

3. Final Answer:

   void UpdateObject(ref MyClass obj) { obj = new MyClass(); } -> Option B

4. Quick Check:

   Use ref to reassign reference type parameter [OK]

Hint: Use ref keyword to let method reassign caller's reference [OK]

Common Mistakes:

• Using no keyword and expecting reassignment to affect caller
• Confusing out and ref keywords
• Trying to reassign with in parameter

3. What is the output of the following C# code?

class Person {
  public string Name;
}

void ChangeName(Person p) {
  p.Name = "Alice";
  p = new Person();
  p.Name = "Bob";
}

Person person = new Person();
person.Name = "John";
ChangeName(person);
Console.WriteLine(person.Name);

medium

A. John

B. null

C. Bob

D. Alice

Solution

1. Step 1: Trace property change before reassignment

   The method sets p.Name = "Alice", changing the original object's Name to "Alice".

2. Step 2: Reassignment inside method does not affect caller

   Then p is assigned a new Person object with Name "Bob", but this does not affect the original reference outside the method.

3. Final Answer:

   Alice -> Option D

4. Quick Check:

   Property change affects original; reassignment does not [OK]

Hint: Property changes affect original; reassignment inside method does not [OK]

Common Mistakes:

• Thinking reassignment changes original reference
• Expecting output to be 'Bob'
• Ignoring property change before reassignment

4. Identify the error in the following code that tries to update a reference type parameter so the caller sees the new object:

class Data {
  public int Value;
}

void ResetData(Data d) {
  d = new Data();
  d.Value = 0;
}

Data data = new Data();
data.Value = 5;
ResetData(data);
Console.WriteLine(data.Value);

medium

A. The method should use ref keyword to reassign the caller's reference.

B. The method should not create a new object inside.

C. The method should assign d.Value = 5 instead of 0.

D. The method should return the new object instead of void.

Solution

1. Step 1: Understand reassignment effect without ref

   Assigning d = new Data() inside the method only changes the local copy of the reference, not the caller's variable.

2. Step 2: Fix by using ref keyword

   Using ref in the method parameter and call allows the method to reassign the caller's reference to the new object.

3. Final Answer:

   The method should use ref keyword to reassign the caller's reference. -> Option A

4. Quick Check:

   Use ref to reassign reference type parameter [OK]

Hint: Use ref keyword to let method reassign caller's reference [OK]

Common Mistakes:

• Expecting reassignment without ref to affect caller
• Thinking returning new object is required
• Confusing property assignment with reference reassignment

5. You want a method to update a reference type parameter's properties and also optionally replace the whole object with a new one, so the caller sees all changes. Which approach correctly achieves this in C#?

hard

A. Pass the object with out keyword; assign new object inside method but do not modify properties.

B. Pass the object normally and modify properties; reassigning inside method updates caller automatically.

C. Pass the object with ref keyword; modify properties and reassign new object inside method.

D. Pass the object with in keyword; modify properties but cannot reassign the object.

Solution

1. Step 1: Understand property modification vs reassignment

   Modifying properties affects original object without ref, but reassignment does not affect caller unless ref is used.

2. Step 2: Use ref to allow both property changes and reassignment

   Passing with ref lets method modify properties and replace the object so caller sees all changes.

3. Final Answer:

   Pass the object with ref keyword; modify properties and reassign new object inside method. -> Option C

4. Quick Check:

   Use ref to modify and reassign reference type parameter [OK]

Hint: Use ref to modify properties and reassign object in method [OK]

Common Mistakes:

• Assuming normal pass allows reassignment to affect caller
• Using out when input object is needed
• Using in which forbids reassignment