Question

Which of the following are benefits of using immutable lists in Kotlin? Select all that apply.


You can select more than one option.


Allows storing more items than mutable lists.



Prevents accidental modification of data.



It reduces the risk of errors in your program.



Provides better performance than mutable lists.



Ensures thread safety due to no changes being allowed.

Answer 1

Correct choices:
- Prevents accidental modification of data.
- It reduces the risk of errors in your program.
- Ensures thread safety due to no changes being allowed.

Why:
- Immutable lists prevent code from changing their contents, so you avoid accidental mutation and many classes of bugs.
- Fewer mutable states generally reduce the chance of errors (easier reasoning, simpler invariants).
- Because they cannot be modified, immutable objects are inherently safer to share across threads.

Why the others are incorrect:
- "Allows storing more items than mutable lists." — false; immutability does not increase capacity.
- "Provides better performance than mutable lists." — not generally true; performance depends on implementation and use case (sometimes immutable structures are faster, sometimes slower).

Note: In Kotlin, the List<T> interface is read-only; to get true immutability you must ensure the underlying collection is not mutated (for example by only exposing an immutable collection or using truly immutable implementations).