Performance implications of boxing in C Sharp (C#) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is boxing in C#?

Boxing is the process of converting a value type (like int) to an object type, wrapping the value inside a heap-allocated object.

beginner

Why can boxing cause performance issues?

Boxing creates a new object on the heap and copies the value, which uses extra memory and CPU time, and can increase garbage collection pressure.

intermediate

What happens during unboxing?

Unboxing extracts the value type from the boxed object, which requires type checking and copying the value back, adding overhead.

intermediate

How can you avoid boxing in C#?

Use generic types or methods, or work directly with value types instead of casting them to object types.

beginner

What is a real-life analogy for boxing?

Imagine putting a small item (value type) into a box (object) to carry it around. This takes extra effort and space compared to carrying the item directly.

What does boxing do in C#?

A Deletes a value type

B Converts a value type to an object type

C Converts an object type to a value type

D Optimizes memory usage automatically

Boxing wraps a value type inside an object, converting it to an object type.

Which of these is a performance cost of boxing?

A Heap allocation and copying of value

B Faster execution time

C No memory usage

D Automatic inlining

Boxing creates a new object on the heap and copies the value, which costs time and memory.

How can you reduce boxing in your code?

A Use generics to work with value types directly

B Always cast value types to object

C Use dynamic typing

D Avoid using value types

Generics allow working with value types without boxing.

What is unboxing?

A Converting a value type to string

B Copying a reference type

C Deleting an object

D Extracting a value type from a boxed object

Unboxing extracts the original value type from the boxed object.

Which scenario causes boxing?

A Using a generic List<int>

B Using an int directly

C Assigning an int to an object variable

D Declaring a string variable

Assigning a value type like int to an object causes boxing.

Explain what boxing is and why it can affect performance in C#.

Think about how value types become objects.

Describe two ways to avoid boxing in your C# programs.

Consider how to keep values as value types.

Practice

1. What is boxing in C#?

easy

A. Converting a value type to an object type

B. Converting an object type to a value type

C. Copying a reference type to another reference

D. Converting a string to a number

Solution

1. Step 1: Understand value and object types

   Value types hold data directly, object types hold references to data.

2. Step 2: Define boxing

   Boxing wraps a value type inside an object so it can be treated as an object.

3. Final Answer:

   Converting a value type to an object type -> Option A

4. Quick Check:

   Boxing = value type to object [OK]

Hint: Boxing wraps value types as objects to use object features [OK]

Common Mistakes:

• Confusing boxing with unboxing
• Thinking boxing converts reference types
• Assuming boxing changes the value itself

2. Which of the following code snippets causes boxing in C#?

easy

A. int x = 5; object o = x;

B. int x = 5; int y = x + 2;

C. string s = "hello"; object o = s;

D. int[] arr = new int[3];

Solution

1. Step 1: Identify boxing operation

   Boxing happens when a value type is assigned to an object type.

2. Step 2: Analyze each option

   int x = 5; object o = x; assigns int (value type) to object, causing boxing. Others do not.

3. Final Answer:

   int x = 5; object o = x; -> Option A

4. Quick Check:

   Value type to object assignment = boxing [OK]

Hint: Assigning value type to object causes boxing [OK]

Common Mistakes:

• Thinking string to object is boxing (string is reference type)
• Confusing array creation with boxing
• Assuming arithmetic operations cause boxing

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

int i = 10;
object o = i;
int j = (int)o + 5;
Console.WriteLine(j);

medium

A. 10

B. Runtime error

C. 15

D. Compilation error

Solution

1. Step 1: Understand boxing and unboxing here

   int i is boxed into object o. Then unboxed back to int j with cast.

2. Step 2: Calculate the output

   j = (int)o + 5 = 10 + 5 = 15, printed by Console.WriteLine.

3. Final Answer:

   15 -> Option C

4. Quick Check:

   Unboxing and addition = 15 [OK]

Hint: Unbox with cast, then add normally [OK]

Common Mistakes:

• Forgetting to cast during unboxing causing runtime error
• Assuming boxing changes the value
• Expecting output to be 10 or error

4. Identify the error in this code related to boxing/unboxing:

object o = 42;
int x = o;

medium

A. Cannot assign int to object

B. Missing explicit cast during unboxing

C. Boxing not allowed for int

D. No error, code is correct

Solution

1. Step 1: Check assignment from object to int

   Unboxing requires explicit cast from object to value type.

2. Step 2: Identify missing cast

   Code assigns object to int without cast, causing compile error.

3. Final Answer:

   Missing explicit cast during unboxing -> Option B

4. Quick Check:

   Unboxing needs cast [OK]

Hint: Unboxing always needs explicit cast [OK]

Common Mistakes:

• Assuming implicit cast works for unboxing
• Confusing boxing with unboxing errors
• Thinking boxing is disallowed for int

5. You want to improve performance by avoiding boxing in this code:

List<object> list = new List<object>();
for (int i = 0; i < 5; i++) {
    list.Add(i);
}
int sum = 0;
foreach (int x in list) {
    sum += x;
}
Console.WriteLine(sum);

What is the best way to avoid boxing here?

hard

A. No change needed, boxing is minimal

B. Cast each element to int before adding

C. Use object array instead of List

D. Use List<int> instead of List<object>

Solution

1. Step 1: Identify boxing cause

   Adding int to List<object> boxes each int to object.

2. Step 2: Use generic List of int

   Using List<int> stores ints directly, no boxing occurs.

3. Final Answer:

   Use List<int> instead of List<object> -> Option D

4. Quick Check:

   Generic list of value type avoids boxing [OK]

Hint: Use generic collections with value types to avoid boxing [OK]

Common Mistakes:

• Casting before adding does not avoid boxing
• Using object array still boxes ints
• Ignoring boxing impact on performance