Bird
Raised Fist0
Kotlinprogramming~3 mins

Why Multiple type parameters in Kotlin? - Purpose & Use Cases

Choose your learning style10 modes available
The Big Idea

What if you could write one class that works perfectly for any two things you want to pair?

The Scenario

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.

The Problem

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.

The Solution

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.

Before vs After
✗ Before
class BookAndBookmark(val book: Book, val bookmark: Bookmark)
class ToyAndBox(val toy: Toy, val box: Box)
✓ After
class Pair<A, B>(val first: A, val second: B)
What It Enables

You can create reusable, flexible code that works with any types, making your programs smarter and easier to maintain.

Real Life Example

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.

Key Takeaways

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

(1/5)
1. What does it mean when a Kotlin function has <T, U> before its name?
easy
A. The function is limited to only one type parameter named T or U.
B. The function can only accept types T or U but not both at the same time.
C. The function uses two different type parameters, T and U, to work with multiple types.
D. The function automatically converts types T and U to String.

Solution

  1. Step 1: Understand type parameters in Kotlin

    Type parameters like <T, U> allow a function to accept multiple types, making it flexible.
  2. Step 2: Interpret the meaning of <T, U>

    Having <T, U> means the function can work with two different types, T and U, independently.
  3. Final Answer:

    The function uses two different type parameters, T and U, to work with multiple types. -> Option C
  4. Quick Check:

    Multiple type parameters = flexible function types [OK]
Hint: Multiple type parameters mean multiple flexible types [OK]
Common Mistakes:
  • Thinking it limits to only one type at a time
  • Assuming automatic type conversion happens
  • Confusing type parameters with actual types
2. Which of the following is the correct syntax to declare a Kotlin function with two type parameters named T and U?
easy
A. fun myFunction(param1: T, param2: U) {}
B. fun myFunction(param1: T, param2: U) {}
C. fun myFunction(param1: T, param2: U) {}
D. fun myFunction(param1: T, param2: U) {}

Solution

  1. Step 1: Recall Kotlin generic function syntax

    Type parameters are declared immediately after the fun keyword inside angle brackets, separated by commas.
  2. 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.
  3. Final Answer:

    fun <T, U> myFunction(param1: T, param2: U) {} -> Option A
  4. Quick Check:

    Type parameters go after fun with commas [OK]
Hint: Type parameters come right after fun, separated by commas [OK]
Common Mistakes:
  • Missing comma between type parameters
  • Placing type parameters after function name
  • Putting type parameters after parameter list
3. What is the output of this Kotlin code?
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)
}
medium
A. Compilation error
B. Pair(10, cats)
C. cats and 10
D. 10 and cats

Solution

  1. 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.
  2. Step 2: Trace the main function call

    pairToString is called with Pair(10, "cats"), so pair.first = 10 and pair.second = "cats".
  3. Final Answer:

    10 and cats -> Option D
  4. Quick Check:

    pair.first + " and " + pair.second = "10 and cats" [OK]
Hint: Read pair.first and pair.second values carefully [OK]
Common Mistakes:
  • Swapping first and second values
  • Expecting Pair's default toString output
  • Thinking it causes a compilation error
4. Identify the error in this Kotlin function declaration:
fun <T, U> combine(a: T, b: U): T {
    return b
}
medium
A. Return type T does not match returned value b of type U.
B. Missing comma between T and U in type parameters.
C. Function must return type U instead of T.
D. No error, the function is correct.

Solution

  1. Step 1: Check function return type and return statement

    The function declares return type T but returns b which is of type U.
  2. Step 2: Understand type mismatch error

    Returning U where T is expected causes a type mismatch compilation error.
  3. Final Answer:

    Return type T does not match returned value b of type U. -> Option A
  4. Quick Check:

    Return type must match returned value type [OK]
Hint: Return type must match the returned value type [OK]
Common Mistakes:
  • Ignoring type mismatch between T and U
  • Assuming Kotlin auto-converts types
  • Missing comma in type parameters (not the case here)
5. You want to create a Kotlin generic class 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?
hard
A. class Box<T>(val first: T, val second: T) { fun getFirst(): T = first fun getSecond(): T = second }
B. class Box(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second }
C. class Box { val first: T val second: U }
D. class Box(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second }

Solution

  1. 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.
  2. 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.
  3. Final Answer:

    class Box<T, U>(val first: T, val second: U) { fun getFirst(): T = first fun getSecond(): U = second } -> Option B
  4. Quick Check:

    Multiple type parameters with matching properties and methods [OK]
Hint: Use and matching properties for both types [OK]
Common Mistakes:
  • Using only one type parameter for both items
  • Not declaring type parameters in class header
  • Using undefined types without generics
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard