What if you could safely use anything without knowing exactly what it is?
Why Star projection for unknown types in Kotlin? - Purpose & Use Cases
Imagine you have a box with many different toys, but you don't know exactly which toys are inside. You want to play safely without breaking anything, but you can't see or guess the exact toy type.
Trying to handle each toy manually means guessing its type or risking errors. You might try to treat a toy as a car when it's actually a doll, causing confusion and mistakes in your code.
Star projection lets you say, "I don't know the exact type, but I want to work safely with whatever is inside." It acts like a safe cover that hides the unknown details but still lets you use the box without errors.
fun printList(list: List<Any>) {
for (item in list) {
println(item)
}
}fun printList(list: List<*>) {
for (item in list) {
println(item)
}
}It enables you to write flexible and safe code that works with any type without knowing the details upfront.
When you receive a list from a library but don't know what type of items it holds, star projection lets you process the list safely without errors or crashes.
Star projection helps handle unknown types safely.
It prevents errors when working with generic types you don't know.
It makes your code more flexible and robust.
Practice
* represent in Kotlin generics?Solution
Step 1: Understand star projection meaning
The star projection*means an unknown generic type in Kotlin.Step 2: Analyze its usage
It allows safe reading from generic collections but restricts writing to avoid type errors.Final Answer:
An unknown generic type that allows safe reading but restricts writing -> Option DQuick Check:
Star projection = unknown generic type with safe read [OK]
- Thinking star projection allows writing to generics
- Confusing star projection with specific generic types
- Assuming star projection only works with primitives
Solution
Step 1: Recall star projection syntax
Star projection uses*inside angle brackets to represent unknown type.Step 2: Check each option
val list: List<*> = listOf(1, 2, 3) usesList<*>which is correct syntax for star projection.Final Answer:
val list: List<*> = listOf(1, 2, 3) -> Option BQuick Check:
Star projection syntax = List<*> [OK]
- Leaving angle brackets empty like List<>
- Using List<Any> which is not star projection
- Confusing star projection with out-projection
fun printFirst(list: List<*>) {
println(list[0])
}
fun main() {
val numbers: List<Int> = listOf(10, 20, 30)
printFirst(numbers)
}Solution
Step 1: Understand star projection usage in function
The function acceptsList<*>, meaning unknown generic type, safe to read elements.Step 2: Analyze the call with List<Int>
PassingList<Int>is valid; readinglist[0]returns 10 safely.Final Answer:
10 -> Option AQuick Check:
Reading from List<*> returns element safely [OK]
- Assuming star projection causes compile error
- Expecting null instead of actual element
- Thinking runtime exception occurs on read
fun addElement(list: MutableList<*>, element: Any) {
list.add(element)
}Solution
Step 1: Understand star projection with MutableList
MutableList<*> means unknown generic type; writing is restricted to avoid type errors.Step 2: Analyze the add operation
Trying to addelementcauses compile error because type is unknown and unsafe to write.Final Answer:
Cannot add element to MutableList<*> due to unknown type -> Option CQuick Check:
Writing to MutableList<*> causes error [OK]
- Thinking add works with MutableList<*>
- Confusing syntax error with type error
- Assuming Any type is always accepted
List<*> to a MutableList<Any> in Kotlin?Solution
Step 1: Understand star projection restrictions
List<*> allows safe reading but elements are of unknown type, so direct assignment to MutableList<Any> is unsafe.Step 2: Safely copy elements
Use a loop to read each element and cast to Any before adding to MutableList<Any>, ensuring type safety.Final Answer:
Use a loop to cast each element to Any and add to MutableList<Any> -> Option AQuick Check:
Copy with loop and cast = safe transfer [OK]
- Trying direct assignment between incompatible generic types
- Using star projection on mutable list incorrectly
- Ignoring type casting when copying elements
Ready to prove it?
Pass the test and this pattern moves unknown
