Why immutable collections are default in Kotlin - See It in Action

Why Immutable Collections Are Default in Kotlin

📖 Scenario: Imagine you are managing a list of favorite fruits in a Kotlin app. You want to keep this list safe from accidental changes by other parts of your program.

🎯 Goal: You will create an immutable list of fruits, then try to add a fruit to it, and finally print the list to see that it has not changed. This will help you understand why Kotlin uses immutable collections by default.

📋 What You'll Learn

Create an immutable list called fruits with these exact items: "Apple", "Banana", "Cherry"

Create a variable called newFruit and set it to "Orange"

Try to add newFruit to fruits using the plus function and save the result in updatedFruits

Print fruits and updatedFruits to show the original list is unchanged and the new list has the added fruit

💡 Why This Matters

🌍 Real World

Immutable collections are used in apps to keep important data safe from accidental changes, like user settings or fixed lists.

💼 Career

Understanding immutability is important for writing reliable Kotlin code and working with modern Android apps or backend services.

1

Create an immutable list of fruits

Create an immutable list called fruits with these exact items: "Apple", "Banana", "Cherry"

Kotlin

// Create an immutable list called fruits with "Apple", "Banana", "Cherry"
// Your code here

Hint

Use listOf to create an immutable list in Kotlin.

2

Create a new fruit variable

Create a variable called newFruit and set it to "Orange"

Kotlin

val fruits = listOf("Apple", "Banana", "Cherry")
// Create a variable newFruit and set it to "Orange"
// Your code here

Hint

Use val to create a read-only variable.

3

Add the new fruit to the list immutably

Use the plus function to add newFruit to fruits and save the result in a new variable called updatedFruits

Kotlin

val fruits = listOf("Apple", "Banana", "Cherry")
val newFruit = "Orange"
// Use plus to add newFruit to fruits and save in updatedFruits
// Your code here

Hint

The plus function or + operator returns a new list without changing the original.

4

Print both lists to see the difference

Print fruits and updatedFruits using println to show the original list is unchanged and the new list has the added fruit

Kotlin

val fruits = listOf("Apple", "Banana", "Cherry")
val newFruit = "Orange"
val updatedFruits = fruits + newFruit
// Print fruits and updatedFruits
// Your code here

Hint

Use println to display the lists.

Practice

1. Why does Kotlin use immutable collections as the default choice?

easy

A. Because they prevent accidental changes and make code safer

B. Because they are faster to create than mutable collections

C. Because they allow adding elements after creation

D. Because they use less memory than mutable collections

Solution

1. Step 1: Understand immutability concept

   Immutable collections cannot be changed after creation, preventing accidental modifications.

2. Step 2: Recognize safety benefits

   This immutability makes programs safer and easier to understand by avoiding unexpected side effects.

3. Final Answer:

   Because they prevent accidental changes and make code safer -> Option A

4. Quick Check:

   Immutable collections = safer code [OK]

Hint: Immutable means no changes allowed after creation [OK]

Common Mistakes:

• Thinking immutable collections allow adding elements
• Assuming immutable collections are always faster
• Confusing immutability with memory usage

2. Which of the following is the correct way to create an immutable list in Kotlin?

easy

A. val list = ArrayList(1, 2, 3)

B. val list = mutableListOf(1, 2, 3)

C. val list = arrayListOf(1, 2, 3)

D. val list = listOf(1, 2, 3)

Solution

1. Step 1: Identify immutable list creation function

   In Kotlin, listOf() creates an immutable list.

2. Step 2: Differentiate from mutable list functions

   mutableListOf(), arrayListOf(), and ArrayList() create mutable lists.

3. Final Answer:

   val list = listOf(1, 2, 3) -> Option D

4. Quick Check:

   Immutable list = listOf() [OK]

Hint: Use listOf() for immutable lists in Kotlin [OK]

Common Mistakes:

• Using mutableListOf() when immutable is needed
• Confusing arrayListOf() with immutable listOf()
• Trying to use ArrayList constructor with elements directly

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

val numbers = listOf(1, 2, 3)
numbers.add(4)

medium

A. List will contain [1, 2, 3, 4]

B. Compilation error: Unresolved reference 'add'

C. Runtime error: UnsupportedOperationException

D. List remains [1, 2, 3] without error

Solution

1. Step 1: Recognize listOf creates immutable list

   The listOf() function returns an immutable list that does not support modification methods like add().

2. Step 2: Understand behavior of calling add() on immutable list

   Calling add() on a List<T> causes a compilation error because List<T> has no add() method: Unresolved reference 'add'.

3. Final Answer:

   Compilation error: Unresolved reference 'add' -> Option B

4. Quick Check:

   Immutable list + add() = compile error [OK]

Hint: Immutable lists have no add() method: compile error [OK]

Common Mistakes:

• Expecting runtime error instead of compile-time error
• Assuming add() works on immutable lists
• Thinking list remains unchanged silently

4. Identify the error in this Kotlin code snippet:

val set = setOf(1, 2, 3)
set.add(4)

medium

A. Runtime error: UnsupportedOperationException when calling add()

B. Syntax error: setOf cannot be used without mutable keyword

C. Compile-time error: add() is not a function of Set

D. No error, set will contain 4 elements

Solution

1. Step 1: Understand setOf creates immutable set

   The setOf() function returns an immutable set that does not support modification.

2. Step 2: Analyze calling add() on immutable set

   Calling add() on a Set<T> causes a compile-time error because Set<T> has no add() method.

3. Final Answer:

   Compile-time error: add() is not a function of Set -> Option C

4. Quick Check:

   Immutable set + add() = compile error [OK]

Hint: Immutable sets have no add() method: compile error [OK]

Common Mistakes:

• Expecting runtime error instead of compile-time error
• Assuming setOf creates mutable sets
• Thinking add() silently fails without error

5. You want to create a map in Kotlin that cannot be changed after creation. Which approach correctly ensures immutability and prevents accidental modification?

hard

A. Use mapOf() to create an immutable map

B. Use mutableMapOf() and avoid calling modification methods

C. Create a mutable map and then assign it to a val variable

D. Use HashMap() and do not expose it outside the function

Solution

1. Step 1: Identify immutable map creation method

   mapOf() creates an immutable map that cannot be changed after creation.

2. Step 2: Understand why other options fail

   Using mutableMapOf() or HashMap() creates mutable maps; assigning to val only prevents reassignment, not modification.

3. Final Answer:

   Use mapOf() to create an immutable map -> Option A

4. Quick Check:

   Immutable map = mapOf() [OK]

Hint: Use mapOf() for truly immutable maps in Kotlin [OK]

Common Mistakes:

• Thinking val prevents map modification
• Using mutableMapOf() expecting immutability
• Relying on scope to protect mutable maps