Nullable receiver extensions in Kotlin - Step-by-Step Execution

Concept Flow - Nullable receiver extensions

Call extension on nullable receiver

↓

Check if receiver is null?

Yes→Return null or default

No↓

Execute extension function body

↓

Return result

When calling an extension on a nullable receiver, Kotlin checks if the receiver is null before running the extension code. If null, it can return null or a default value.

Execution Sample

Kotlin

fun String?.shout() = this?.uppercase()

val name: String? = null
println(name.shout())

Defines an extension on a nullable String that returns uppercase or null, then calls it on a null value.

Execution Table

Step	Receiver (this)	Check null?	Action	Result
1	null	Is null?	Yes	Return null
2	null	Extension call ends	-	null printed

💡 Receiver is null, so extension returns null without running uppercase()

Variable Tracker

Variable	Start	After call	Final
name	null	null	null
this (receiver)	null	null	null
result	undefined	null	null

Key Moments - 2 Insights

Why does the extension return null instead of throwing an error when receiver is null?

Because the extension uses safe call (this?.uppercase()), it checks for null and returns null early as shown in execution_table step 1.

What happens if we call the extension on a non-null string?

The extension runs uppercase() on the string and returns the uppercase version, as the null check in execution_table step 1 would be No.

Visual Quiz - 3 Questions

Look at the execution table, what is the result when the receiver is null?

A null

B Empty string

C Throws NullPointerException

D Original string

💡 Hint

See execution_table row 1 where receiver is null and result is null

At which step does the extension decide not to run uppercase()?

A Before step 1

B Step 2

C Step 1

D After step 2

💡 Hint

Check execution_table step 1 where null check returns Yes and skips uppercase()

If the receiver was "hello", what would the result be?

A "hello"

B "HELLO"

C null

D Throws error

💡 Hint

Based on variable_tracker and concept_flow, non-null receiver runs uppercase()

Concept Snapshot

Nullable receiver extensions:
- Define with receiver type nullable (e.g., String?)
- Use safe calls inside extension (this?.method())
- If receiver is null, extension returns null or default
- Prevents NullPointerException on null receivers
- Allows calling extensions safely on nullable objects

Full Transcript

This visual trace shows how Kotlin handles nullable receiver extensions. When you call an extension function on a nullable receiver, Kotlin first checks if the receiver is null. If it is null, the extension returns null or a default value without running the function body. For example, the extension 'shout' on String? uses a safe call 'this?.uppercase()'. When called on null, it returns null immediately. The execution table shows step 1 checking null and returning null, and step 2 ending the call. The variable tracker shows the receiver and result values. This prevents errors and lets you safely call extensions on nullable objects.

Practice

1. What is the main benefit of using nullable receiver extensions in Kotlin?

easy

A. They prevent any null values from being assigned.

B. They make variables non-nullable automatically.

C. They convert nullable types to non-nullable types permanently.

D. They allow calling functions on nullable types without explicit null checks.

Solution

1. Step 1: Understand nullable receiver extensions

   Nullable receiver extensions let you add functions to types that can be null, so you can call these functions safely without extra null checks.

2. Step 2: Identify the benefit

   This means you can write cleaner code by calling functions directly on nullable objects without risking null pointer exceptions.

3. Final Answer:

   They allow calling functions on nullable types without explicit null checks. -> Option D

4. Quick Check:

   Nullable receiver extensions = call on nullable safely [OK]

Hint: Nullable extensions handle null inside function, no extra checks needed [OK]

Common Mistakes:

• Thinking they convert nullable to non-nullable permanently
• Assuming they prevent null assignments
• Confusing with regular extensions on non-null types

2. Which of the following is the correct syntax to define a nullable receiver extension function isNullOrEmpty for String? in Kotlin?

easy

A. fun String.isNullOrEmpty(): Boolean = this == null || this.isEmpty()

B. fun String.isNullOrEmpty?(): Boolean = this == null || this.isEmpty()

C. fun String?.isNullOrEmpty(): Boolean = this == null || this.isEmpty()

D. fun String?.isNullOrEmpty?(): Boolean = this == null || this.isEmpty()

Solution

1. Step 1: Identify nullable receiver syntax

   To define an extension on a nullable type, use String? as the receiver type with a question mark after the type name.

2. Step 2: Check function syntax

   The function name should not have a question mark. So fun String?.isNullOrEmpty() is correct.

3. Final Answer:

   fun String?.isNullOrEmpty(): Boolean = this == null || this.isEmpty() -> Option C

4. Quick Check:

   Nullable receiver = question mark after type [OK]

Hint: Nullable receiver extension uses ? after type, not after function name [OK]

Common Mistakes:

• Putting ? after function name instead of receiver type
• Missing ? on receiver type for nullable
• Using non-nullable receiver for nullable extension

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

fun String?.describe(): String = this ?: "Empty"

fun main() {
  val text1: String? = "Hello"
  val text2: String? = null
  println(text1.describe())
  println(text2.describe())
}

medium

A. Hello\nEmpty

B. Hello\nnull

C. null\nEmpty

D. Empty\nEmpty

Solution

1. Step 1: Understand the extension function behavior

   The function returns the string itself if not null, otherwise returns "Empty".

2. Step 2: Apply to variables

   text1 is "Hello", so describe() returns "Hello". text2 is null, so describe() returns "Empty".

3. Final Answer:

   Hello\nEmpty -> Option A

4. Quick Check:

   Nullable describe returns value or "Empty" [OK]

Hint: ?: operator returns left if not null, else right [OK]

Common Mistakes:

• Assuming null prints as "null" string
• Confusing ?: with !! operator
• Expecting function to throw on null

4. Identify the error in this Kotlin code using a nullable receiver extension:

fun String?.firstChar(): Char = this[0]

fun main() {
  val s: String? = null
  println(s.firstChar())
}

medium

A. Compilation error: Extension function syntax incorrect

B. Compilation error: Cannot call get(0) on nullable receiver without null check

C. No error, prints first character or null

D. Runtime exception: NullPointerException when calling firstChar on null

Solution

1. Step 1: Analyze extension function code

   The function calls this[0] on a nullable receiver String? without a null check or safe call.

2. Step 2: Understand compiler behavior

   Kotlin compiler detects the unsafe access on nullable receiver and produces a compilation error.

3. Final Answer:

   Compilation error: Cannot call get(0) on nullable receiver without null check -> Option B

4. Quick Check:

   Unsafe access on nullable receiver = compile error [OK]

Hint: Nullable receiver extensions must check for null before use [OK]

Common Mistakes:

• Assuming nullable receiver is auto-checked
• Thinking it causes runtime exception instead of compilation error
• Thinking it compiles and prints null instead of error

5. You want to create a nullable receiver extension safeLength() for String? that returns the string length or zero if null. Which implementation is correct and safe?

1) fun String?.safeLength() = this.length ?: 0
2) fun String?.safeLength() = this?.length ?: 0
3) fun String.safeLength() = this.length ?: 0
4) fun String?.safeLength() = if (this == null) null else this.length

hard

A. Option 2

B. Option 1

C. Option 3

D. Option 4

Solution

1. Step 1: Check each option for null safety

   Option 1 calls this.length directly on nullable this, causing error. Option 3 uses non-nullable receiver, so not valid for nullable. Option 4 returns null instead of Int zero.

2. Step 2: Identify correct safe call usage

   Option 2 uses safe call this?.length which returns length or null, then ?: 0 returns zero if null. This is safe and returns Int.

3. Final Answer:

   fun String?.safeLength() = this?.length ?: 0 -> Option A

4. Quick Check:

   Safe call ?. with ?: zero fallback is correct pattern [OK]

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

Common Mistakes:

• Calling length directly on nullable without safe call
• Using non-nullable receiver for nullable extension
• Returning null instead of zero for null input