Trailing lambda convention in Kotlin - Step-by-Step Execution

Concept Flow - Trailing lambda convention

Call function with lambda

↓

Is lambda last argument?

No→Call normally

Yes↓

Use trailing lambda syntax

↓

Execute lambda block

↓

Return from function

The trailing lambda convention lets you pass a lambda outside the parentheses if it's the last argument, making code cleaner.

Execution Sample

Kotlin

fun greet(action: () -> Unit) {
    println("Hello")
    action()
}

greet {
    println("Welcome!")
}

Defines a function taking a lambda and calls it using trailing lambda syntax.

Execution Table

Step	Action	Output	Notes
1	Call greet with trailing lambda		Lambda passed outside parentheses
2	Print "Hello"	Hello	First print in greet()
3	Execute lambda block	Welcome!	Lambda prints "Welcome!"
4	Return from greet		Function ends

💡 Function greet completes after executing lambda passed as trailing argument

Variable Tracker

Variable	Start	After greet call	After lambda execution	Final
action	N/A	lambda function	executed	N/A

Key Moments - 2 Insights

Why can we write the lambda outside the parentheses?

Because the lambda is the last argument, Kotlin allows trailing lambda syntax to improve readability, as shown in step 1 of the execution_table.

What happens if the lambda is not the last argument?

You must pass the lambda inside the parentheses; trailing lambda syntax only works if the lambda is the last argument.

Visual Quiz - 3 Questions

Look at the execution_table, what is printed at step 3?

A "Hello"

B "Welcome!"

C Nothing

D An error

💡 Hint

Check the Output column at step 3 in the execution_table

At which step does the lambda function get executed?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the Action column in the execution_table for when the lambda block runs

If the lambda was not the last argument, how would the call change?

A Lambda would still be outside parentheses

B Lambda would be omitted

C Lambda must be inside parentheses

D Function call would fail

💡 Hint

Refer to key_moments about lambda position and syntax

Concept Snapshot

Trailing lambda convention in Kotlin:
- If the last argument is a lambda, write it outside parentheses.
- Makes code cleaner and more readable.
- Only works if lambda is last argument.
- Example: greet { println("Welcome!") }

Full Transcript

This example shows Kotlin's trailing lambda convention. The function greet takes a lambda as its only argument. When calling greet, the lambda is written outside the parentheses, making the call cleaner. Execution steps show printing "Hello", then running the lambda which prints "Welcome!". The lambda variable is assigned at call and executed inside the function. This convention only works if the lambda is the last argument. If not, the lambda must be inside the parentheses.

Practice

1. What is the main purpose of the trailing lambda convention in Kotlin?

easy

A. To allow placing the lambda expression outside the parentheses when it is the last argument

B. To require all lambda expressions to be inside parentheses

C. To prevent using lambda expressions as function arguments

D. To force lambda expressions to be declared as variables before use

Solution

1. Step 1: Understand the trailing lambda convention and compare options

   The trailing lambda convention lets you write a lambda expression outside the parentheses if it is the last argument of a function. Only "To allow placing the lambda expression outside the parentheses when it is the last argument" correctly describes this behavior. Other options contradict the convention.

2. Final Answer:

   To allow placing the lambda expression outside the parentheses when it is the last argument -> Option A

3. Quick Check:

   Trailing lambda = lambda outside parentheses [OK]

Hint: Last lambda argument can go outside parentheses [OK]

Common Mistakes:

• Thinking lambdas must always be inside parentheses
• Confusing trailing lambda with lambda variable declaration
• Believing trailing lambda disallows lambdas as arguments

2. Which of the following Kotlin function calls correctly uses the trailing lambda convention?

easy

A. list.filter { it > 0 }

B. list.filter({ it > 0 })

C. list.filter(it > 0)

D. list.filter it > 0

Solution

1. Step 1: Identify correct trailing lambda syntax and check other options

   Trailing lambda means the lambda is placed outside the parentheses. list.filter { it > 0 } shows this correctly. list.filter({ it > 0 }) uses lambda inside parentheses (valid but not trailing). list.filter(it > 0) and D are syntax errors.

2. Final Answer:

   list.filter { it > 0 } -> Option A

3. Quick Check:

   Trailing lambda = lambda outside parentheses [OK]

Hint: Trailing lambda goes after parentheses, no extra parentheses needed [OK]

Common Mistakes:

• Putting lambda inside parentheses when trailing lambda is expected
• Omitting parentheses incorrectly
• Writing lambda without braces

3. What is the output of this Kotlin code?

fun greet(action: () -> String) = println(action())
greet { "Hello, Kotlin!" }

medium

A. No output

B. kotlin.Unit

C. Syntax error

D. Hello, Kotlin!

Solution

1. Step 1: Understand the function call and evaluate the output

   The function greet takes a lambda returning a String and prints its result. The call uses trailing lambda syntax. The lambda returns "Hello, Kotlin!" which is printed by println.

2. Final Answer:

   Hello, Kotlin! -> Option D

3. Quick Check:

   Trailing lambda call prints lambda result [OK]

Hint: Trailing lambda calls run the lambda and print result [OK]

Common Mistakes:

• Expecting syntax error due to trailing lambda
• Confusing return value with Unit
• Missing that println prints the lambda result

4. Identify the error in this Kotlin code using trailing lambda:

fun calculate(x: Int, operation: (Int) -> Int): Int {
    return operation(x)
}

val result = calculate(5) operation { it * 2 }

medium

A. Missing parentheses around lambda argument

B. Incorrect function declaration

C. Trailing lambda must be outside parentheses but parentheses are missing

D. No error, code is correct

Solution

1. Step 1: Analyze the function call syntax and correct trailing lambda usage

   The function call calculate(5) operation { it * 2 } is invalid because the trailing lambda must be placed immediately after the parentheses without extra tokens. The correct call is calculate(5) { it * 2 }. The word operation should not appear between parentheses and lambda.

2. Final Answer:

   Trailing lambda must be outside parentheses but parentheses are missing -> Option C

3. Quick Check:

   Trailing lambda goes right after parentheses [OK]

Hint: Trailing lambda must follow parentheses directly, no extra tokens [OK]

Common Mistakes:

• Inserting parameter name between parentheses and lambda
• Forgetting to remove parentheses when using trailing lambda
• Confusing function parameter names with call syntax

5. Given this Kotlin function:

fun processNumbers(numbers: List<Int>, filter: (Int) -> Boolean, action: (Int) -> Unit) {
    for (number in numbers) {
        if (filter(number)) action(number)
    }
}

Which is the correct way to call processNumbers using trailing lambda convention for both lambdas?

hard

A. processNumbers(listOf(1,2,3)) { it > 1 } { println(it) }

B. processNumbers(listOf(1,2,3), { it > 1 }) { println(it) }

C. processNumbers(listOf(1,2,3)) { println(it) } { it > 1 }

D. processNumbers(listOf(1,2,3), { println(it) }, { it > 1 })

Solution

1. Step 1: Understand trailing lambda rules for multiple lambdas and apply to function call

   Kotlin allows only the last lambda argument to be passed outside parentheses as a trailing lambda. Since action is the last lambda, it can be trailing. The first lambda filter must be inside parentheses. processNumbers(listOf(1,2,3), { it > 1 }) { println(it) } correctly places filter inside parentheses and action outside.

2. Final Answer:

   processNumbers(listOf(1,2,3), { it > 1 }) { println(it) } -> Option B

3. Quick Check:

   Only last lambda can be trailing [OK]

Hint: Only last lambda argument goes outside parentheses [OK]

Common Mistakes:

• Trying to put multiple lambdas outside parentheses
• Swapping lambda order incorrectly
• Putting non-lambda arguments outside parentheses