Why null safety is Kotlin's defining feature - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Kotlin code with null safety?

Consider the following Kotlin code snippet. What will it print when run?

Kotlin

fun main() {
    val name: String? = null
    println(name?.length ?: "No name")
}

A Throws NullPointerException

B 0

C null

D No name

💡 Hint

Look at the safe call operator and the Elvis operator usage.

The variable 'name' is nullable (String?). The safe call operator '?.' checks if 'name' is null before accessing 'length'. Since 'name' is null, the Elvis operator '?:' returns "No name" instead of throwing an error.

🧠 Conceptual

intermediate

Why does Kotlin distinguish between nullable and non-nullable types?

Why is it important that Kotlin has separate types for nullable and non-nullable variables?

A To allow variables to change type at runtime

B To prevent null pointer exceptions by forcing explicit handling of nulls

C To make all variables nullable by default

D To make the code run faster by avoiding null checks

💡 Hint

Think about common errors in other languages caused by null values.

Kotlin's type system forces developers to explicitly handle nullable types, which helps avoid null pointer exceptions that are common in many other languages.

🔧 Debug

advanced

What error does this Kotlin code produce?

Examine the code below. What error will the Kotlin compiler report?

Kotlin

fun main() {
    val text: String = null
    println(text.length)
}

A Null can not be a value of a non-null type String

B Unresolved reference: length

C NullPointerException at runtime

D No error, prints 0

💡 Hint

Look at the variable declaration and its assigned value.

The variable 'text' is declared as a non-nullable String but assigned null, which is not allowed. The compiler reports a type mismatch error.

📝 Syntax

advanced

Which Kotlin code snippet correctly uses the safe call operator?

Select the code snippet that safely accesses the length of a nullable String variable 'input'.

A val length = input?.length

B val length = input ?: input.length

C val length = input!! .length

D val length = input.length

💡 Hint

Safe call operator is used with '?.' syntax.

Option A uses the safe call operator '?.' which safely accesses 'length' only if 'input' is not null, otherwise returns null.

🚀 Application

expert

What is the output of this Kotlin code demonstrating null safety with let?

Analyze the following Kotlin code and select the output it produces.

Kotlin

fun main() {
    val name: String? = "Kotlin"
    name?.let {
        println("Name length is ${it.length}")
    } ?: println("Name is null")
}

A Name is null

B Name length is null

C Name length is 6

D Throws NullPointerException

💡 Hint

The 'let' function runs only if the variable is not null.

Since 'name' is not null, the 'let' block executes and prints the length of the string 'Kotlin' which is 6.

Practice

1. What is the main purpose of Kotlin's null safety feature?

easy

A. To allow all variables to be null by default

B. To prevent errors caused by accessing null values

C. To make Kotlin code run faster

D. To remove the need for variable declarations

Solution

1. Step 1: Understand null safety concept

   Kotlin's null safety is designed to avoid null pointer exceptions by making null handling explicit.

2. Step 2: Identify the main purpose

   The main goal is to prevent errors caused by accessing null values, which are common bugs in many languages.

3. Final Answer:

   To prevent errors caused by accessing null values -> Option B

4. Quick Check:

   Null safety = prevent null errors [OK]

Hint: Null safety means avoiding null errors in code [OK]

Common Mistakes:

• Thinking null safety allows all variables to be null
• Believing it improves performance directly
• Confusing null safety with removing declarations

2. Which of the following is the correct way to declare a nullable variable in Kotlin?

easy

A. val name: String? = null

B. val name: String = null

C. val name: String! = null

D. val name: String = ?null

Solution

1. Step 1: Recall Kotlin nullable syntax

   In Kotlin, adding a question mark after the type makes it nullable, allowing it to hold null.

2. Step 2: Check each option

   val name: String? = null uses String? which is correct. Others are invalid syntax or do not allow null.

3. Final Answer:

   val name: String? = null -> Option A

4. Quick Check:

   Nullable type uses ? after type [OK]

Hint: Use ? after type to allow nulls in Kotlin [OK]

Common Mistakes:

• Omitting the ? for nullable types
• Using invalid symbols like ! or ?null
• Assigning null to non-nullable types

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

val name: String? = null
println(name?.length ?: "No name")

medium

A. Throws NullPointerException

B. 0

C. null

D. No name

Solution

1. Step 1: Understand safe call and Elvis operator

   The safe call ?. returns null if name is null. The Elvis operator ?: provides a default value if the left side is null.

2. Step 2: Evaluate the expression

   Since name is null, name?.length is null, so the expression returns "No name".

3. Final Answer:

   No name -> Option D

4. Quick Check:

   Safe call + Elvis = default value [OK]

Hint: Safe call ?. returns null, Elvis ?: gives default [OK]

Common Mistakes:

• Expecting NullPointerException
• Thinking length of null is 0
• Confusing safe call with normal call

4. Identify the error in this Kotlin code snippet:

val length = name.length
val name: String? = null

medium

A. Variable 'name' is used before declaration

B. No error, code runs fine

C. Missing semicolon after declaration

D. Cannot access length on nullable variable without safe call

Solution

1. Step 1: Analyze variable usage order

   The variable name is used before it is declared.

2. Step 2: Identify the compile error

   Kotlin requires variables to be declared before use, causing an unresolved reference error.

3. Final Answer:

   Variable 'name' is used before declaration -> Option A

4. Quick Check:

   Declare before use [OK]

Hint: Declare variables before using them in Kotlin [OK]

Common Mistakes:

• Thinking it's only a null safety issue
• Believing the code runs fine
• Assuming Kotlin requires semicolons

5. How can you safely call a function printLength that prints the length of a nullable String text without causing a NullPointerException?

hard

A. fun printLength(text: String) { println(text.length) }
printLength(null)

B. fun printLength(text: String?) { println(text.length) }
printLength(null)

C. fun printLength(text: String?) { println(text?.length ?: 0) }
printLength(null)

D. fun printLength(text: String) { println(text?.length) }
printLength(null)

Solution

1. Step 1: Understand function parameter nullability

   To accept null, parameter must be String?. Options A and D use non-nullable String, so passing null causes error.

2. Step 2: Use safe call and default value

   fun printLength(text: String?) { println(text?.length ?: 0) } printLength(null) uses safe call ?. and Elvis operator ?: to print 0 if text is null, avoiding exceptions.

3. Final Answer:

   fun printLength(text: String?) { println(text?.length ?: 0) } printLength(null) -> Option C

4. Quick Check:

   Safe call + Elvis handles null safely [OK]

Hint: Use ?. and ?: to safely handle nullable parameters [OK]

Common Mistakes:

• Passing null to non-nullable parameter
• Accessing length without safe call
• Ignoring default value for null case