Why Chaining scope functions in Kotlin? - Purpose & Use Cases

The Big Idea

What if you could do many things to an object in one simple, readable flow without repeating yourself?

The Scenario

Imagine you have a list of tasks to do, and you want to update each task's status, print it, and then save it. Doing each step separately means writing repetitive code for each task.

The Problem

Writing separate code for each step is slow and easy to mess up. You might forget to update a task before printing or save the wrong version. It becomes hard to read and maintain.

The Solution

Chaining scope functions lets you do multiple actions on the same object in a clean, readable way. You can update, print, and save a task all in one smooth flow without repeating the object name.

Before vs After

✗ Before

task.status = "Done"
println(task)
saveTask(task)

✓ After

task.apply {
  status = "Done"
  println(this)
}.also { saveTask(it) }

What It Enables

It enables writing clear, concise code that flows naturally, making complex object operations easy and error-free.

Real Life Example

When configuring a user profile, you can set the name, update preferences, and log the changes all in one chain, making your code neat and simple.

Key Takeaways

Manual steps cause repetitive and error-prone code.

Chaining scope functions lets you perform many actions on one object smoothly.

This makes code easier to read, write, and maintain.

Practice

1. What does chaining scope functions in Kotlin help you achieve?

easy

A. Perform multiple operations on one object without repeating its name

B. Create multiple objects at once

C. Write loops faster

D. Automatically convert types

Solution

1. Step 1: Understand the purpose of scope functions

   Scope functions let you run code blocks on an object, often returning the object or a result.

2. Step 2: Recognize chaining benefit

   Chaining lets you call many scope functions one after another on the same object without repeating its name.

3. Final Answer:

   Perform multiple operations on one object without repeating its name -> Option A

4. Quick Check:

   Chaining scope functions = clean, repeated operations [OK]

Hint: Chaining avoids repeating object names in multiple calls [OK]

Common Mistakes:

• Thinking chaining creates new objects
• Confusing chaining with loops
• Believing chaining changes data types automatically

2. Which of the following is the correct syntax to chain apply and also on an object obj?

easy

A. obj.apply { }.also { }

B. obj.apply() also()

C. apply(obj) { } also { }

D. obj.apply { } also { }

Solution

1. Step 1: Recall correct chaining syntax

   In Kotlin, scope functions are called with dot notation and lambda blocks inside curly braces.

2. Step 2: Check each option

   obj.apply { }.also { } uses correct dot chaining with braces. obj.apply() also() misses dots and braces. apply(obj) { } also { } uses wrong function call style. obj.apply { } also { } misses dot before also.

3. Final Answer:

   obj.apply { }.also { } -> Option A

4. Quick Check:

   Dot + braces = correct chaining syntax [OK]

Hint: Use dot and braces for each scope function call [OK]

Common Mistakes:

• Omitting dots between functions
• Using parentheses instead of braces for lambdas
• Calling scope functions like regular functions without object

3. What is the output of this Kotlin code?

val result = "hello".also { println(it.uppercase()) }.length
println(result)

medium

A. hello\n5

B. 5\nHELLO

C. HELLO\nhello

D. HELLO\n5

Solution

1. Step 1: Understand also behavior

   also runs the lambda with the object as it, prints uppercase "HELLO", then returns the original string "hello".

2. Step 2: Calculate result

   After also, length is called on "hello", which is 5. Then println(result) prints 5.

3. Final Answer:

   HELLO 5 -> Option D

4. Quick Check:

   also prints uppercase, length returns 5 [OK]

Hint: also returns original object, so length is on original string [OK]

Common Mistakes:

• Thinking also returns uppercase string
• Confusing print order
• Expecting length to be printed before uppercase

4. Find the error in this Kotlin code chaining scope functions:

val text = "kotlin"
text.let { it.uppercase() }.apply { println(this) }

medium

A. apply cannot be called after let because let returns a different type

B. Missing lambda braces in apply

C. let does not return the original object, so apply prints wrong value

D. No error, code works fine

Solution

1. Step 1: Analyze let return value

   let returns the lambda result, here it.uppercase(), a new String "KOTLIN".

2. Step 2: Check apply receiver

   apply is called on the uppercase string, so this inside apply is "KOTLIN" and println(this) prints "KOTLIN".

3. Step 3: Identify the problem

   The original text is "kotlin", but apply prints the uppercase string, not the original. This may be unexpected if you want to print original.

4. Final Answer:

   let does not return the original object, so apply prints wrong value -> Option C

5. Quick Check:

   let returns lambda result, not original object [OK]

Hint: Remember let returns lambda result, not original object [OK]

Common Mistakes:

• Assuming let returns original object
• Thinking apply needs braces
• Believing no error exists

5. Given a mutable list val nums = mutableListOf(1, 2, 3), which chained scope function call correctly adds 4, prints the list, and returns the updated list?

hard

A. nums.let { it.add(4) }.also { println(it) }

B. nums.apply { add(4) }.also { println(it) }

C. nums.also { add(4) }.apply { println(this) }

D. nums.run { add(4); println(this) }

Solution

1. Step 1: Understand return values of scope functions

   apply returns the original object after running the block, also returns the original object too, let returns lambda result, run returns lambda result.

2. Step 2: Check each option

   nums.apply { add(4) }.also { println(it) } adds 4 inside apply, then prints list in also, returning the updated list. nums.let { it.add(4) }.also { println(it) }'s let returns Unit from add, so also prints Unit. nums.also { add(4) }.apply { println(this) } has syntax error ('add' unresolved in also block, needs it.add(4)). nums.run { add(4); println(this) } returns Unit from run.

3. Final Answer:

   nums.apply { add(4) }.also { println(it) } -> Option B

4. Quick Check:

   apply returns object, also prints it [OK]

Hint: Use apply to modify and also to print, both return original object [OK]

Common Mistakes:

• Using let which returns Unit from add
• Expecting run to return the list
• Confusing order of operations in chaining