Why generics provide type safety in Kotlin

Introduction

Generics help catch mistakes early by making sure you only use the right types with your code. This keeps your program safe and avoids errors.

When you want to create a list that only holds one type of item, like only numbers or only words.

When writing a function that works with different types but should keep the type consistent.

When you want to avoid mistakes by mixing different types in collections or classes.

When you want your code to be reusable but still safe from type errors.

Syntax

Kotlin

class Box<T>(val value: T) {
    fun getValue(): T {
        return value
    }
}

T is a placeholder for any type you want to use.

You specify the actual type when creating an object, like Box for integers.

Examples

Here, intBox only holds integers and stringBox only holds strings.

Kotlin

val intBox = Box<Int>(123)
val stringBox = Box<String>("hello")

This function can print any type, but keeps the type consistent for each call.

Kotlin

fun <T> printItem(item: T) {
    println(item)
}

Sample Program

This program shows two boxes holding different types safely. Trying to put the wrong type causes an error before running.

Kotlin

class Box<T>(val value: T) {
    fun getValue(): T {
        return value
    }
}

fun main() {
    val intBox = Box<Int>(123)
    val stringBox = Box<String>("hello")

    println(intBox.getValue())
    println(stringBox.getValue())

    // The following line would cause a compile error if uncommented:
    // intBox.value = "wrong type"
}

Important Notes

Generics help find errors while writing code, not when running it.

They make your code flexible and safe at the same time.

Summary

Generics keep your code safe by checking types early.

They let you write reusable code that works with many types.

Using generics prevents mixing wrong types and bugs.

Practice

1. Why do generics in Kotlin help provide type safety?

easy

A. They automatically convert types at runtime.

B. They allow any type without restrictions.

C. They make the program run faster.

D. They check types at compile time to prevent errors.

Solution

1. Step 1: Understand generics role in type checking

   Generics allow specifying the type a class or function works with, so the compiler can check if the correct type is used.

2. Step 2: Identify how this prevents errors

   By checking types early, generics prevent mixing incompatible types, avoiding bugs before running the program.

3. Final Answer:

   They check types at compile time to prevent errors. -> Option D

4. Quick Check:

   Generics = Compile-time type checks [OK]

Hint: Generics catch wrong types before running code [OK]

Common Mistakes:

• Thinking generics allow any type without checks
• Believing generics speed up runtime
• Confusing compile-time and runtime type checks

2. Which of the following is the correct syntax to declare a generic class in Kotlin?

easy

A. class Box { var value: T }

B. class Box<T> { var value: T }

C. class Box<T> { var value: Int }

D. class Box<T> (value: T) : T

Solution

1. Step 1: Review generic class syntax

   In Kotlin, generic classes declare a type parameter inside angle brackets after the class name, like class Box<T>.

2. Step 2: Check property type usage

   The property inside should use the generic type T, not a fixed type like Int.

3. Final Answer:

   class Box<T> { var value: T } -> Option B

4. Quick Check:

   Generic class syntax = class Box<T> { var value: T } [OK]

Hint: Generic type goes in angle brackets after class name [OK]

Common Mistakes:

• Using fixed types instead of generic type parameter
• Omitting the generic type parameter declaration
• Incorrect inheritance syntax with generics

3. What will be the output of this Kotlin code?

fun main() {
    val list: List<String> = listOf("apple", "banana")
    val first: String = list[0]
    println(first.length)
}

medium

A. Syntax error

B. Runtime error

C. 5

D. 0

Solution

1. Step 1: Understand the list type and access

   The list is declared as List<String>, so it only holds strings. Accessing list[0] returns "apple".

2. Step 2: Calculate the length of the first string

   "apple" has 5 characters, so first.length is 5, which is printed.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   "apple" length = 5 [OK]

Hint: Check type and value before output [OK]

Common Mistakes:

• Confusing list element type causing errors
• Expecting runtime error due to generics
• Miscounting string length

4. Identify the error in this Kotlin code using generics:

fun printFirst(list: List<Int>) {
    val first = list[0]
    println(first.length)
}

medium

A. Cannot call length on Int type

B. List<Int> cannot be indexed

C. Missing generic type declaration

D. Function return type is missing

Solution

1. Step 1: Analyze the list element type

   The list holds Int values, so first is an integer.

2. Step 2: Check the method called on the element

   Calling length on an integer is invalid because Int does not have a length property.

3. Final Answer:

   Cannot call length on Int type -> Option A

4. Quick Check:

   Int has no length property [OK]

Hint: Check methods valid for the generic type used [OK]

Common Mistakes:

• Assuming all types have length property
• Thinking indexing List<Int> is invalid
• Ignoring type mismatch errors

5. How do generics prevent mixing wrong types in Kotlin collections? Consider this code:

val numbers: MutableList<Number> = mutableListOf(1, 2.5, 3)
numbers.add(4.0f)
numbers.add("five")

What happens and why?

hard

A. Compilation error on adding "five" because it's not a Number

B. All values added successfully, no errors

C. Runtime error when adding 4.0f

D. Compilation error on adding 4.0f because it's a Float

Solution

1. Step 1: Understand the collection type

   The list is declared as MutableList<Number>, so it accepts any subtype of Number like Int, Double, Float.

2. Step 2: Check the added elements

   Adding 4.0f (a Float) is allowed because Float is a Number subtype. Adding "five" (a String) causes a compile-time error because String is not a Number.

3. Final Answer:

   Compilation error on adding "five" because it's not a Number -> Option A

4. Quick Check:

   Generics block wrong types at compile time [OK]

Hint: Only add types matching generic parameter [OK]

Common Mistakes:

• Thinking all types can be added to Number list
• Confusing runtime and compile-time errors
• Assuming Float is not a Number subtype