Type inference by the compiler in Kotlin - Mini Project: Build & Apply

Type inference by the compiler

📖 Scenario: You are creating a simple Kotlin program to understand how the compiler can guess the type of variables without you telling it explicitly.

🎯 Goal: Build a Kotlin program that shows how the compiler infers types for different variables and prints their values.

📋 What You'll Learn

Create variables without specifying their types explicitly

Assign values of different types to these variables

Print the values of these variables

💡 Why This Matters

🌍 Real World

Type inference helps programmers write cleaner and faster code by letting the compiler figure out types automatically.

💼 Career

Understanding type inference is important for Kotlin developers to write idiomatic and efficient code in Android and backend development.

1

Create variables with inferred types

Create three variables called number, text, and flag and assign them the values 42, "Hello", and true respectively without specifying their types.

Kotlin

# Create variables number, text, and flag with values 42, "Hello", and true
# Your code here

Hint

Use val to declare variables and assign values directly without specifying types.

2

Add a variable with a floating-point value

Create a variable called price and assign it the value 19.99 without specifying its type.

Kotlin

val number = 42
val text = "Hello"
val flag = true
# Create variable price with value 19.99
# Your code here

Hint

Just assign 19.99 to price using val without a type.

3

Add a variable with a list of integers

Create a variable called numbers and assign it a list of integers listOf(1, 2, 3, 4, 5) without specifying its type.

Kotlin

val number = 42
val text = "Hello"
val flag = true
val price = 19.99
# Create variable numbers with listOf(1, 2, 3, 4, 5)
# Your code here

Hint

Use listOf to create a list and assign it to numbers.

4

Print all variables

Print the values of number, text, flag, price, and numbers using println.

Kotlin

val number = 42
val text = "Hello"
val flag = true
val price = 19.99
val numbers = listOf(1, 2, 3, 4, 5)
# Print all variables
# Your code here

Hint

Use println for each variable to show its value on the screen.

Practice

1. What does type inference mean in Kotlin?

easy

A. The compiler automatically figures out the variable's type.

B. You must always specify the variable type manually.

C. The program runs slower because types are guessed at runtime.

D. It means variables cannot change their values.

Solution

1. Step 1: Understand type inference concept

   Type inference means the compiler looks at the value assigned and decides the variable's type automatically.

2. Step 2: Compare options with definition

   Only The compiler automatically figures out the variable's type. correctly describes this automatic type detection by the compiler.

3. Final Answer:

   The compiler automatically figures out the variable's type. -> Option A

4. Quick Check:

   Type inference = automatic type detection [OK]

Hint: Type inference means no need to write types explicitly [OK]

Common Mistakes:

• Thinking types are guessed at runtime
• Believing you must always write types
• Confusing type inference with variable mutability

2. Which of the following Kotlin variable declarations uses type inference correctly?

easy

A. val number: String = 10

B. val number: Int = "10"

C. val number = 10

D. val number =

Solution

1. Step 1: Check each declaration for correctness

   val number = 10 assigns 10 to 'number' without specifying type, so compiler infers Int type correctly.

2. Step 2: Identify errors in other options

   val number: Int = "10" assigns a String to Int type explicitly - error. val number: String = 10 assigns Int to String type - error. val number = is incomplete syntax.

3. Final Answer:

   val number = 10 -> Option C

4. Quick Check:

   Correct syntax with inferred type = val number = 10 [OK]

Hint: Look for variable with value but no explicit type [OK]

Common Mistakes:

• Mixing types in assignment
• Leaving declaration incomplete
• Assigning wrong type to explicit type

3. What is the inferred type of result in this Kotlin code?

val result = listOf(1, 2, 3).map { it * 2 }

medium

A. Array<Int>

B. List<Int>

C. Int

D. List<String>

Solution

1. Step 1: Analyze the expression assigned to result

   listOf(1, 2, 3) creates a List<Int>. The map function multiplies each element by 2, so the result is a List<Int>.

2. Step 2: Confirm the inferred type

   Since map returns a List of the transformed elements, the inferred type is List<Int>.

3. Final Answer:

   List<Int> -> Option B

4. Quick Check:

   Mapping Int list with Int operation = List<Int> [OK]

Hint: map keeps list type, changes element type if needed [OK]

Common Mistakes:

• Confusing List with Array
• Thinking map returns a single Int
• Assuming type changes to String

4. Identify the error in this Kotlin code snippet related to type inference:

val x = null
val y = x + 5

medium

A. Cannot add Int to null value

B. x cannot be null without explicit type

C. Type inference infers x as Int automatically

D. No error, code runs fine

Solution

1. Step 1: Understand type inference for null assignment

   Assigning null without type makes x's type Nothing?, which cannot be used in arithmetic.

2. Step 2: Check the operation y = x + 5

   Adding 5 to null is invalid; Kotlin does not allow arithmetic with null values.

3. Final Answer:

   Cannot add Int to null value -> Option A

4. Quick Check:

   Arithmetic with null causes error [OK]

Hint: Null needs explicit type; can't do math with null [OK]

Common Mistakes:

• Assuming null has Int type
• Ignoring null safety rules
• Thinking code compiles without error

5. Given this Kotlin code, what is the inferred type of data?

val data = mapOf("a" to 1, "b" to 2).mapValues { it.value * 10 }

hard

A. List>

B. List<Int>

C. Map

D. Map

Solution

1. Step 1: Analyze mapOf and mapValues usage

   mapOf creates a Map. mapValues transforms each value by multiplying by 10, keeping keys same.

2. Step 2: Determine the resulting type

   mapValues returns a Map with the same key type and transformed value type, so Map.

3. Final Answer:

   Map -> Option D

4. Quick Check:

   mapValues keeps Map type, changes values [OK]

Hint: mapValues keeps Map type, changes only values [OK]

Common Mistakes:

• Confusing mapValues with map returning List
• Assuming values become Strings
• Thinking result is a List instead of Map