Why wrapper classes are used in Java - Performance Analysis

Time Complexity: Why wrapper classes are used

O(n)

Understanding Time Complexity

We want to understand how using wrapper classes affects the time it takes for a program to run.

Specifically, we ask: How does wrapping a simple value in an object change the work done by the program?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

Integer sum = 0;
for (int i = 1; i <= n; i++) {
    sum += i; // auto-unboxing and boxing happen here
}
System.out.println(sum);
    

This code adds numbers from 1 to n using the Integer wrapper class instead of primitive int.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop runs from 1 to n, adding values.
• How many times: The loop runs n times.
• Additional work: Each addition involves boxing and unboxing Integer objects.

How Execution Grows With Input

As n grows, the loop runs more times, and boxing/unboxing happens each time.

Input Size (n)	Approx. Operations
10	About 10 additions with boxing/unboxing
100	About 100 additions with boxing/unboxing
1000	About 1000 additions with boxing/unboxing

Pattern observation: The work grows directly with n, but each step has extra cost due to wrapper use.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as the input size increases, but using wrappers adds small extra work each step.

Common Mistake

[X] Wrong: "Using wrapper classes does not affect performance because they behave like primitives."

[OK] Correct: Wrappers create objects and need extra steps to convert between objects and primitives, which adds time especially in loops.

Interview Connect

Understanding how wrapper classes impact time helps you write clearer and more efficient code, a skill valued in many programming tasks.

Self-Check

"What if we replaced Integer with int in the loop? How would the time complexity and performance change?"

Practice

1. Why are wrapper classes used in Java?

easy

A. To replace all primitive types with objects

B. To improve the speed of primitive operations

C. To allow primitive types to be treated as objects

D. To create new primitive types

Solution

1. Step 1: Understand primitive vs object types

   Primitive types like int or double are not objects, so they can't be used where objects are required.

2. Step 2: Role of wrapper classes

   Wrapper classes like Integer or Double wrap primitive values so they can be used as objects.

3. Final Answer:

   To allow primitive types to be treated as objects -> Option C

4. Quick Check:

   Wrapper classes = primitive as objects [OK]

Hint: Wrapper classes wrap primitives as objects [OK]

Common Mistakes:

• Thinking wrapper classes speed up primitive operations
• Believing wrapper classes replace primitives entirely
• Confusing wrapper classes with new primitive types

2. Which of the following is the correct way to create an Integer wrapper object from an int value 10?

easy

A. Integer obj = new Integer(10);

B. int obj = Integer(10);

C. Integer obj = new int(10);

D. Integer obj = Integer.value(10);

Solution

1. Step 1: Check syntax for creating Integer object

   The constructor Integer(int) creates an Integer object from an int value.

2. Step 2: Validate each option

   Integer obj = new Integer(10); uses new Integer(10), which is correct syntax. int obj = Integer(10); is invalid syntax. Integer obj = new int(10); is invalid as primitive int has no constructor. Integer obj = Integer.value(10); uses a non-existent method value().

3. Final Answer:

   Integer obj = new Integer(10); -> Option A

4. Quick Check:

   Use new Integer(int) to create wrapper [OK]

Hint: Use new Integer(value) to create wrapper object [OK]

Common Mistakes:

• Using invalid method names like Integer.value()
• Trying to instantiate primitives like new int(10)
• Confusing primitive and wrapper syntax

3. What will be the output of the following code?

List<Integer> list = new ArrayList<>();
list.add(5);
list.add(10);
System.out.println(list.get(0) + list.get(1));

medium

A. 510

B. 15

C. Compilation error

D. Runtime error

Solution

1. Step 1: Understand autoboxing in collections

   List<Integer> stores Integer objects. Adding int values 5 and 10 autoboxes them to Integer objects.

2. Step 2: Evaluate the addition operation

   list.get(0) and list.get(1) return Integer objects, which unbox to int when added, so 5 + 10 = 15.

3. Final Answer:

   15 -> Option B

4. Quick Check:

   Autoboxing/unboxing sums to 15 [OK]

Hint: Autoboxing lets you add Integer values like ints [OK]

Common Mistakes:

• Thinking list.get returns int directly
• Expecting string concatenation instead of addition
• Assuming compilation or runtime errors

4. Identify the error in the following code snippet:

int a = 5;
Integer b = null;
int c = a + b;

medium

A. No error, code runs fine

B. Compilation error due to incompatible types

C. ArithmeticException at runtime

D. NullPointerException at runtime

Solution

1. Step 1: Analyze autounboxing of Integer b

   Variable b is an Integer object set to null. When used in arithmetic, it is unboxed to int.

2. Step 2: Understand null unboxing behavior

   Unboxing null causes NullPointerException at runtime because there is no int value to extract.

3. Final Answer:

   NullPointerException at runtime -> Option D

4. Quick Check:

   Unboxing null Integer causes NullPointerException [OK]

Hint: Unboxing null wrapper causes NullPointerException [OK]

Common Mistakes:

• Expecting compilation error instead of runtime error
• Assuming code runs without error
• Confusing NullPointerException with ArithmeticException

5. You want to store primitive int values in a collection and perform arithmetic operations easily. Which approach best uses wrapper classes to achieve this?

hard

A. Use List<Integer> and rely on autoboxing/unboxing

B. Use List<int> since it stores primitives directly

C. Convert int to String before adding to collection

D. Use arrays only, wrapper classes are not needed

Solution

1. Step 1: Understand collections and primitives

   Java collections cannot store primitive types like int directly; they require objects.

2. Step 2: Use wrapper classes with autoboxing

   List<Integer> stores Integer objects. Autoboxing converts int to Integer automatically, allowing easy arithmetic with unboxing.

3. Final Answer:

   Use List<Integer> and rely on autoboxing/unboxing -> Option A

4. Quick Check:

   Collections need wrapper classes for primitives [OK]

Hint: Use List<Integer> for primitives with autoboxing [OK]

Common Mistakes:

• Trying to use List<int> which is invalid
• Storing primitives as Strings unnecessarily
• Avoiding wrapper classes in collections