What if you could write one class that works perfectly for any two things you want to pair?
Why Multiple type parameters in Kotlin? - Purpose & Use Cases
Imagine you want to create a box that can hold two different things, like a book and a bookmark. You try to write separate classes for each pair of types, like BookAndBookmark, ToyAndBox, and so on.
This manual way means writing many classes for every combination. It's slow, boring, and easy to make mistakes. If you want to change something, you must update many places. It's like copying and pasting the same code again and again.
Using multiple type parameters lets you write one flexible class that can hold any two types. You just say what types you want when you use it. This saves time, reduces errors, and keeps your code clean and easy to change.
class BookAndBookmark(val book: Book, val bookmark: Bookmark) class ToyAndBox(val toy: Toy, val box: Box)
class Pair<A, B>(val first: A, val second: B)You can create reusable, flexible code that works with any types, making your programs smarter and easier to maintain.
Think of a shopping app where you want to pair a product with its discount. Using multiple type parameters, you can create a single Pair class to hold any product and any discount type without writing new classes for each.
Manual coding for each type pair is slow and error-prone.
Multiple type parameters let you write one flexible class for many types.
This approach saves time and keeps code clean and reusable.
Practice
<T, U> before its name?Solution
Step 1: Understand type parameters in Kotlin
Type parameters like <T, U> allow a function to accept multiple types, making it flexible.Step 2: Interpret the meaning of <T, U>
Having <T, U> means the function can work with two different types, T and U, independently.Final Answer:
The function uses two different type parameters, T and U, to work with multiple types. -> Option CQuick Check:
Multiple type parameters = flexible function types [OK]
- Thinking it limits to only one type at a time
- Assuming automatic type conversion happens
- Confusing type parameters with actual types
Solution
Step 1: Recall Kotlin generic function syntax
Type parameters are declared immediately after the fun keyword inside angle brackets, separated by commas.Step 2: Check each option's syntax
fun myFunction(param1: T, param2: U) {} correctly uses <T, U> after fun and before the function name, matching Kotlin syntax.Final Answer:
fun <T, U> myFunction(param1: T, param2: U) {} -> Option AQuick Check:
Type parameters go after fun with commas [OK]
- Missing comma between type parameters
- Placing type parameters after function name
- Putting type parameters after parameter list
fun <T, U> pairToString(pair: Pair<T, U>): String {
return "${pair.first} and ${pair.second}"
}
fun main() {
val result = pairToString(Pair(10, "cats"))
println(result)
}Solution
Step 1: Understand the function behavior
The function takes a Pair with types T and U, then returns a string combining first and second values.Step 2: Trace the main function call
pairToString is called with Pair(10, "cats"), so pair.first = 10 and pair.second = "cats".Final Answer:
10 and cats -> Option DQuick Check:
pair.first + " and " + pair.second = "10 and cats" [OK]
- Swapping first and second values
- Expecting Pair's default toString output
- Thinking it causes a compilation error
fun <T, U> combine(a: T, b: U): T {
return b
}Solution
Step 1: Check function return type and return statement
The function declares return type T but returns b which is of type U.Step 2: Understand type mismatch error
Returning U where T is expected causes a type mismatch compilation error.Final Answer:
Return type T does not match returned value b of type U. -> Option AQuick Check:
Return type must match returned value type [OK]
- Ignoring type mismatch between T and U
- Assuming Kotlin auto-converts types
- Missing comma in type parameters (not the case here)
Box that can hold two different types of items, T and U. Which of the following class declarations correctly uses multiple type parameters and allows storing and retrieving both items?Solution
Step 1: Check correct multiple type parameter declaration
class Box(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second } declares class Box with <T, U> and constructor parameters of types T and U, which is correct.Step 2: Verify methods to retrieve both items
class Box(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second } provides getFirst() returning T and getSecond() returning U, matching stored types.Final Answer:
class Box<T, U>(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second } -> Option BQuick Check:
Multiple type parameters with matching properties and methods [OK]
- Using only one type parameter for both items
- Not declaring type parameters in class header
- Using undefined types without generics
Ready to prove it?
Pass the test and this pattern moves unknown
