Boxing and unboxing execution in C Sharp (C#) - Time & Space Complexity

Time Complexity: Boxing and unboxing execution

O(n)

Understanding Time Complexity

When we use boxing and unboxing in C#, it's important to know how much work the computer does behind the scenes.

We want to see how the time needed changes as we box and unbox more values.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int[] numbers = new int[n];
object[] boxedNumbers = new object[n];

// Boxing each int
for (int i = 0; i < n; i++) {
    boxedNumbers[i] = numbers[i];
}

// Unboxing each object back to int
for (int i = 0; i < n; i++) {
    int value = (int)boxedNumbers[i];
}
    

This code boxes each integer into an object, then unboxes each object back to an integer.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Two separate loops each running from 0 to n.
• How many times: Each loop runs exactly n times, boxing and unboxing each element once.

How Execution Grows With Input

As the number of elements n grows, the total work grows in a straight line.

Input Size (n)	Approx. Operations
10	About 20 boxing/unboxing steps
100	About 200 boxing/unboxing steps
1000	About 2000 boxing/unboxing steps

Pattern observation: The work doubles when n doubles, showing a steady, linear increase.

Final Time Complexity

Time Complexity: O(n)

This means the time needed grows directly in proportion to how many items we box and unbox.

Common Mistake

[X] Wrong: "Boxing and unboxing happen instantly with no extra cost."

[OK] Correct: Each boxing and unboxing step takes time because it creates or extracts objects, so doing many of them adds up.

Interview Connect

Understanding how boxing and unboxing affect performance shows you know how data types and memory work together, a useful skill for writing efficient code.

Self-Check

"What if we replaced the array of objects with a generic List<int>? How would the time complexity change?"

Practice

1. What happens during boxing in C#?

easy

A. A value type is converted to an object type.

B. An object type is converted to a value type.

C. A reference type is converted to a value type.

D. A value type is converted to a string.

Solution

1. Step 1: Understand boxing concept

   Boxing means wrapping a value type (like int) inside an object so it can be treated as an object.

2. Step 2: Identify the conversion direction

   Boxing converts a value type to an object type, not the other way around.

3. Final Answer:

   A value type is converted to an object type. -> Option A

4. Quick Check:

   Boxing = value type to object [OK]

Hint: Boxing wraps value types as objects [OK]

Common Mistakes:

• Confusing boxing with unboxing
• Thinking boxing converts to string
• Mixing up value and reference types

2. Which of the following is the correct syntax to unbox an object to an int in C#?

easy

A. int x = obj.ToInt();

B. int x = obj as int;

C. int x = Convert.ToInt32(obj);

D. int x = (int)obj;

Solution

1. Step 1: Recall unboxing syntax

   Unboxing requires an explicit cast from object to the original value type.

2. Step 2: Check each option

   int x = (int)obj; uses explicit cast (int)obj which is correct. int x = obj as int; uses 'as' which works only for reference types. int x = Convert.ToInt32(obj); converts but is not unboxing. int x = obj.ToInt(); is invalid syntax.

3. Final Answer:

   int x = (int)obj; -> Option D

4. Quick Check:

   Unboxing = explicit cast (int)obj [OK]

Hint: Unboxing needs explicit cast (int)obj [OK]

Common Mistakes:

• Using 'as' keyword for unboxing
• Using Convert.ToInt32 instead of cast
• Calling non-existent methods like ToInt()

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

int a = 10;
object obj = a; // boxing
int b = (int)obj; // unboxing
b += 5;
Console.WriteLine(a);

medium

A. 15

B. 10

C. 5

D. Compilation error

Solution

1. Step 1: Understand boxing and unboxing here

   Variable 'a' is boxed into 'obj'. Then 'obj' is unboxed into 'b'. 'b' is a separate copy.

2. Step 2: Check value changes

   Incrementing 'b' by 5 does not affect 'a'. So 'a' remains 10.

3. Final Answer:

   10 -> Option B

4. Quick Check:

   Boxing copies value; original stays 10 [OK]

Hint: Boxing copies value; original unchanged [OK]

Common Mistakes:

• Assuming 'a' changes when 'b' changes
• Confusing reference and value types
• Thinking boxing links variables

4. Identify the error in this C# code snippet:

object obj = 123;
long l = (long)obj;
Console.WriteLine(l);

medium

A. Invalid cast exception at runtime

B. Compilation error due to missing cast

C. No error, prints 123

D. Null reference exception

Solution

1. Step 1: Analyze boxing and unboxing types

   Boxing stores an int (123) in obj. Unboxing must cast back to int, not long.

2. Step 2: Understand runtime behavior

   Trying to unbox as long causes InvalidCastException because obj holds int, not long.

3. Final Answer:

   Invalid cast exception at runtime -> Option A

4. Quick Check:

   Unboxing type mismatch causes runtime error [OK]

Hint: Unbox only to original value type [OK]

Common Mistakes:

• Casting to different value type than boxed
• Expecting compile-time error instead of runtime
• Ignoring boxing type stored

5. Given a list of integers boxed as objects, how can you sum their values correctly in C#?

List<object> list = new List<object> { 1, 2, 3, 4 };

Which code snippet correctly sums the integers?

hard

A. int sum = 0; foreach (int x in list) sum += x;

B. int sum = 0; foreach (object o in list) sum += (o as int);

C. int sum = 0; foreach (object o in list) sum += (int)o;

D. int sum = list.Sum();

Solution

1. Step 1: Understand list content and types

   List contains objects boxed from ints. To sum, unbox each object to int.

2. Step 2: Evaluate each option

   A: int sum = 0; foreach (int x in list) sum += x; compile error - cannot implicitly convert object to int.
   B: int sum = 0; foreach (object o in list) sum += (o as int); compile error - 'as' cannot be used with non-nullable value types.
   C: int sum = list.Sum(); fails because list is List<object>, no Sum() overload.
   D: int sum = 0; foreach (object o in list) sum += (int)o; unboxes correctly with (int)o.

3. Final Answer:

   int sum = 0; foreach (object o in list) sum += (int)o; -> Option C

4. Quick Check:

   Unbox each object with (int)o to sum [OK]

Hint: Unbox each object with (int)o before summing [OK]

Common Mistakes:

• Trying to foreach as int directly
• Using Sum() on List<object>
• Using 'as' operator for unboxing