Reference assignment and shared state in C Sharp (C#) - Time & Space Complexity

Time Complexity: Reference assignment and shared state

O(1)

Understanding Time Complexity

Let's explore how assigning references affects the time it takes for a program to run.

We want to see how the program's steps grow when we share data between variables.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Box {
    public int Value;
}

void UpdateBox(Box b) {
    b.Value = 10;
}

Box box1 = new Box();
Box box2 = box1; // Reference assignment
UpdateBox(box2);
    

This code creates a box object, assigns its reference to another variable, and updates the value through the second variable.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Simple reference assignment and a single method call.
• How many times: Each operation happens once, no loops or repeated traversals.

How Execution Grows With Input

Since there are no loops or repeated steps, the number of operations stays the same no matter how big the input is.

Input Size (n)	Approx. Operations
10	3 (assign, assign, update)
100	3 (same steps, no change)
1000	3 (still the same)

Pattern observation: The steps do not increase with input size; they stay constant.

Final Time Complexity

Time Complexity: O(1)

This means the program takes the same amount of time no matter how big the input or data is.

Common Mistake

[X] Wrong: "Assigning a reference creates a new copy and takes longer as data grows."

[OK] Correct: Assigning a reference just points to the same data; it does not copy or repeat work, so time stays the same.

Interview Connect

Understanding how references work helps you explain how programs manage data efficiently without extra cost.

Self-Check

"What if the UpdateBox method contained a loop that changed multiple values inside the Box? How would the time complexity change?"

Practice

1. What happens when you assign one reference type variable to another in C#?
ClassA a = new ClassA();
ClassA b = a;

easy

A. Both variables point to the same object in memory.

B. A new copy of the object is created for b.

C. The variables become independent and do not affect each other.

D. The program throws a compile-time error.

Solution

1. Step 1: Understand reference assignment

   Assigning one reference variable to another makes both variables point to the same object in memory.

2. Step 2: Effect of shared reference

   Changes made through either variable affect the same object, so both see the changes.

3. Final Answer:

   Both variables point to the same object in memory. -> Option A

4. Quick Check:

   Reference assignment = shared object [OK]

Hint: Reference variables share the same object after assignment [OK]

Common Mistakes:

• Thinking a new object is created on assignment
• Assuming variables become independent
• Confusing value types with reference types

2. Which of the following is the correct syntax to assign one reference variable to another in C#?

easy

A. int a = b;

B. ClassA a := b;

C. ClassA a == b;

D. ClassA a = new ClassA(); a = b;

Solution

1. Step 1: Identify correct assignment operator

   In C#, the single equals sign (=) is used for assignment, not double equals (==) or :=.

2. Step 2: Check variable types and initialization

   ClassA a = new ClassA(); a = b; correctly declares a reference variable and assigns another reference variable to it.

3. Final Answer:

   ClassA a = new ClassA(); a = b; -> Option D

4. Quick Check:

   Use = for assignment in C# [OK]

Hint: Use single = for assignment, not == or := [OK]

Common Mistakes:

• Using == instead of = for assignment
• Using := which is invalid in C#
• Assigning incompatible types without casting

3. What is the output of the following code?

class Box { public int Value; }
Box box1 = new Box();
box1.Value = 5;
Box box2 = box1;
box2.Value = 10;
Console.WriteLine(box1.Value);

medium

A. 5

B. 0

C. 10

D. Compilation error

Solution

1. Step 1: Understand reference assignment effect

   box2 is assigned to box1, so both point to the same Box object.

2. Step 2: Trace value changes

   Changing box2.Value to 10 changes the shared object, so box1.Value is also 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   Shared reference means shared data [OK]

Hint: Changing one reference changes all pointing to same object [OK]

Common Mistakes:

• Assuming box1.Value stays 5 after box2 changes it
• Confusing reference and value types
• Expecting a compile error due to assignment

4. Identify the error in this code snippet:

class Person { public string Name; }
Person p1 = new Person();
p1.Name = "Alice";
Person p2;
p2.Name = "Bob";
p1 = p2;

medium

A. p2 is used before being assigned an object.

B. Cannot assign p2 to p1 because they are different types.

C. Cannot assign string to Name property.

D. No error, code runs fine.

Solution

1. Step 1: Check variable initialization

   p2 is declared but not assigned an object before accessing p2.Name.

2. Step 2: Understand runtime error

   Accessing p2.Name causes a NullReferenceException because p2 is null.

3. Final Answer:

   p2 is used before being assigned an object. -> Option A

4. Quick Check:

   Uninitialized reference causes runtime error [OK]

Hint: Always initialize reference variables before use [OK]

Common Mistakes:

• Assuming p2 has default object automatically
• Confusing compile-time and runtime errors
• Ignoring null reference exceptions

5. Given this code, what will be the output?

class Data { public int Number; }
Data d1 = new Data() { Number = 1 };
Data d2 = new Data() { Number = 2 };
d1 = d2;
d2.Number = 5;
Console.WriteLine(d1.Number);

hard

A. 2

B. 5

C. 1

D. Compilation error

Solution

1. Step 1: Analyze reference assignment

   d1 is assigned to d2, so both point to the same object with Number initially 2.

2. Step 2: Trace value change through d2

   Changing d2.Number to 5 changes the shared object, so d1.Number is also 5.

3. Final Answer:

   5 -> Option B

4. Quick Check:

   Reference assignment shares object state [OK]

Hint: After assignment, variables share the same object state [OK]

Common Mistakes:

• Thinking d1.Number remains 1 after assignment
• Confusing value and reference types
• Expecting compile errors on assignment