Why immutability by default matters in Kotlin - Performance Analysis

Time Complexity: Why immutability by default matters

O(n)

Understanding Time Complexity

We want to see how choosing immutability by default affects how long a program takes to run.

Does making data unchangeable slow down or speed up our code as it grows?

Scenario Under Consideration

Analyze the time complexity of the following Kotlin code using immutable lists.

fun addElementImmutable(list: List, element: Int): List {
    return list + element
}

fun main() {
    var numbers = listOf(1, 2, 3)
    numbers = addElementImmutable(numbers, 4)
    println(numbers)
}
    

This code adds an element to a list without changing the original list, creating a new list each time.

Identify Repeating Operations

Look at what repeats when adding elements immutably.

• Primary operation: Copying the entire list to create a new one with the added element.
• How many times: Once per addition, the whole list is copied.

How Execution Grows With Input

As the list gets bigger, copying it takes more time.

Input Size (n)	Approx. Operations
10	About 10 copy steps
100	About 100 copy steps
1000	About 1000 copy steps

Pattern observation: The time to add grows directly with the list size because it copies all elements each time.

Final Time Complexity

Time Complexity: O(n)

This means adding an element takes longer as the list grows, because it copies the whole list every time.

Common Mistake

[X] Wrong: "Adding an element to an immutable list is always fast because nothing changes."

[OK] Correct: Even though the original list stays the same, the program must copy all elements to make a new list, which takes more time as the list grows.

Interview Connect

Understanding how immutability affects time helps you explain trade-offs clearly and write safer, predictable code in real projects.

Self-Check

What if we used a persistent data structure that shares parts of the list instead of copying everything? How would the time complexity change?

Practice

1. Why does Kotlin use val for variables by default instead of var?

easy

A. Because val creates immutable variables, making code safer and easier to understand.

B. Because val allows variables to change values anytime.

C. Because var is deprecated in Kotlin.

D. Because val is faster to execute than var.

Solution

1. Step 1: Understand Kotlin's default variable behavior

   Kotlin uses val by default to create immutable variables that cannot be changed after assignment.

2. Step 2: Recognize benefits of immutability

   Immutable variables prevent accidental changes, making code safer and easier to read and maintain.

3. Final Answer:

   Because val creates immutable variables, making code safer and easier to understand. -> Option A

4. Quick Check:

   Immutability = safer code [OK]

Hint: Remember: val means fixed value, var means variable value [OK]

Common Mistakes:

• Thinking val allows value changes
• Believing var is deprecated
• Assuming val is faster than var

2. Which of the following Kotlin declarations correctly creates an immutable variable?

easy

A. var name = "Alice"

B. val name = "Alice"

C. immutable name = "Alice"

D. const var name = "Alice"

Solution

1. Step 1: Identify Kotlin syntax for immutable variables

   Kotlin uses val to declare immutable variables that cannot be reassigned.

2. Step 2: Check each option

   val name = "Alice" uses val correctly. var name = "Alice" uses var which is mutable. The other two options use invalid syntax.

3. Final Answer:

   val name = "Alice" -> Option B

4. Quick Check:

   Immutable variable syntax = val [OK]

Hint: val means immutable, var means mutable [OK]

Common Mistakes:

• Using var instead of val for immutability
• Trying to use 'immutable' keyword
• Combining const and var incorrectly

3. What will be the output of this Kotlin code?

val x = 10
// x = 20
println(x)

medium

A. 20

B. Runtime error

C. 10

D. Compilation error

Solution

1. Step 1: Understand the code behavior

   The variable x is declared with val, so it is immutable and cannot be reassigned.

2. Step 2: Analyze the commented reassignment

   The reassignment x = 20 is commented out, so it does not run. The value of x remains 10.

3. Final Answer:

   10 -> Option C

4. Quick Check:

   Immutable val keeps value 10 [OK]

Hint: Commented code does not run, so value stays same [OK]

Common Mistakes:

• Assuming commented code runs
• Thinking val variables can be reassigned
• Confusing compilation and runtime errors

4. Identify the error in this Kotlin code:

val count = 5
count = 10
println(count)

medium

A. Syntax error: missing semicolon

B. No error, prints 10

C. Runtime error: variable not initialized

D. Compilation error: val cannot be reassigned

Solution

1. Step 1: Check variable declaration

   count is declared with val, making it immutable.

2. Step 2: Analyze reassignment

   Trying to assign count = 10 causes a compilation error because val variables cannot be reassigned.

3. Final Answer:

   Compilation error: val cannot be reassigned -> Option D

4. Quick Check:

   val reassignment = compilation error [OK]

Hint: val variables cannot be reassigned after declaration [OK]

Common Mistakes:

• Thinking val variables can be reassigned
• Confusing runtime and compilation errors
• Assuming semicolons are required in Kotlin

5. You want to create a list of user names that should never change after creation. Which Kotlin declaration is best and why?

val users = listOf("Anna", "Bob", "Cara")

hard

A. Use val with listOf because it creates an immutable list and reference.

B. Use val with mutableListOf to allow adding users later.

C. Use var with listOf because the list can be changed later.

D. Use var with mutableListOf to change the list and reference.

Solution

1. Step 1: Understand immutability of variable and list

   val means the reference cannot change, and listOf creates an immutable list that cannot be modified.

2. Step 2: Compare options

   Use val with listOf because it creates an immutable list and reference. uses val and listOf, ensuring both the reference and list contents cannot change, which matches the requirement.

3. Final Answer:

   Use val with listOf because it creates an immutable list and reference. -> Option A

4. Quick Check:

   val + listOf = fully immutable list [OK]

Hint: val + listOf = fixed list and reference [OK]

Common Mistakes:

• Using var with mutableListOf when immutability is needed
• Confusing mutableListOf with listOf
• Thinking val allows list content changes