We use val to create a reference that cannot be changed to point to another object. This helps keep data safe and predictable.
Val for immutable references in Kotlin
val name: Type = valueval means the reference cannot be reassigned after initialization.
The object the reference points to can still be mutable if its type allows it.
val number: Int = 10
val name = "Alice"
list cannot point to a new list, but the list content can change.val list = mutableListOf(1, 2, 3) list.add(4)
This program shows a val holding a string that cannot be changed. It also shows a val holding a mutable list where the content can change but the reference cannot.
fun main() { val greeting = "Hello" println(greeting) // greeting = "Hi" // This would cause an error val numbers = mutableListOf(1, 2, 3) numbers.add(4) println(numbers) }
Trying to assign a new value to a val variable will cause a compile error.
val protects the reference, not the object itself.
Use var if you need to change the reference to point to something else.
val creates an immutable reference that cannot be reassigned.
The object referenced by val can still be mutable if its type allows.
Using val helps make code safer and easier to understand.
Practice
val keyword do in Kotlin?Solution
Step 1: Understand the role of
valvaldeclares a variable whose reference cannot be changed after assignment.Step 2: Compare with other keywords
varallows reassignment, butvaldoes not.Final Answer:
Creates an immutable reference that cannot be reassigned -> Option BQuick Check:
val= immutable reference [OK]
- Confusing val with var
- Thinking val makes the object itself immutable
- Assuming val declares a function or class
count with value 10 in Kotlin?Solution
Step 1: Identify correct keyword and syntax
valis used for immutable variables, and Kotlin infers type if not specified.Step 2: Check each option
var count = 10 usesvar(mutable), C has invalid syntax, D is incomplete.Final Answer:
val count = 10 -> Option AQuick Check:
Immutable variable syntax = val count = 10 [OK]
- Using var instead of val for immutable variables
- Incorrect Kotlin type declarations
- Leaving declarations incomplete
val list = mutableListOf(1, 2, 3) list.add(4) println(list)
Solution
Step 1: Understand val with mutable objects
valmeans the reference to the list cannot change, but the list itself can be modified.Step 2: Analyze code behavior
Adding 4 to the mutable list changes its content, so printing shows [1, 2, 3, 4].Final Answer:
[1, 2, 3, 4] -> Option DQuick Check:
val reference + mutable object = modified list [OK]
- Thinking val prevents modifying the list content
- Expecting compilation or runtime errors
- Confusing immutable reference with immutable object
val number = 5 number = 10 println(number)
Solution
Step 1: Check reassignment of val variable
valvariables cannot be reassigned after initialization.Step 2: Identify error type
Trying to assign 10 tonumbercauses a compilation error.Final Answer:
Compilation error: val cannot be reassigned -> Option CQuick Check:
val reassignment = compilation error [OK]
- Assuming val variables can be reassigned
- Confusing runtime errors with compile errors
- Ignoring Kotlin's no-semicolon rule
val map = mutableMapOf("a" to 1, "b" to 2)
map["a"] = 3
println(map)Explain why this works even though
map is declared with val.Solution
Step 1: Understand val with mutable collections
valmeans the reference to the map cannot change, but the map's content can be modified.Step 2: Analyze the map update
Updating key "a" to 3 changes the map content, so printing shows {a=3, b=2}.Final Answer:
{a=3, b=2} -> Option AQuick Check:
val reference + mutable map = updated map content [OK]
- Thinking val prevents modifying map content
- Expecting compilation or runtime errors
- Confusing immutable reference with immutable object
Ready to prove it?
Pass the test and this pattern moves unknown
