Why immutable collections are default in Kotlin - Quick Recap

Recall & Review

beginner

What does it mean when a collection is immutable in Kotlin?

An immutable collection cannot be changed after it is created. You cannot add, remove, or update its elements.

beginner

Why are immutable collections the default in Kotlin?

Immutable collections help avoid bugs by preventing accidental changes. They make programs safer and easier to understand.

intermediate

How do immutable collections improve thread safety?

Since immutable collections cannot change, multiple threads can read them without conflicts or the need for locks.

beginner

What is a real-life example to understand immutable collections?

Think of a printed book. Once printed, the pages don’t change. This is like an immutable collection where data stays the same.

beginner

How can you create a mutable collection if needed in Kotlin?

You can use functions like mutableListOf() or mutableMapOf() to create collections that can be changed.

What happens if you try to add an element to an immutable list in Kotlin?

A You get a compile-time error.

B The element is added successfully.

C The program crashes at runtime.

D The list automatically becomes mutable.

Immutable lists do not support adding elements, so Kotlin prevents this at compile time.

Why does Kotlin prefer immutable collections by default?

A To save memory space.

B Because mutable collections are slower.

C To improve safety and reduce bugs.

D Because mutable collections are deprecated.

Immutable collections help avoid accidental changes, making code safer and easier to maintain.

Which of these is a mutable collection in Kotlin?

A listOf()

B mutableListOf()

C setOf()

D mapOf()

mutableListOf() creates a list that can be changed after creation.

How do immutable collections help with multi-threading?

A They automatically synchronize threads.

B They slow down thread execution.

C They prevent any thread from reading data.

D They allow safe concurrent reads without locks.

Immutable collections cannot change, so multiple threads can read them safely at the same time.

Which analogy best describes an immutable collection?

A A printed book that cannot be changed.

B A whiteboard you can erase and rewrite.

C A chalkboard that can be wiped clean.

D A notebook where you can add pages.

A printed book is fixed and cannot be changed, just like an immutable collection.

Explain why Kotlin uses immutable collections as the default choice.

Think about how unchanging data helps avoid mistakes.

Describe a real-life example that helps you understand immutable collections.

Consider something you cannot change once made.