Apply function behavior and use cases in Kotlin - Time & Space Complexity

Time Complexity: Apply function behavior and use cases

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run code using Kotlin's apply function changes as the input grows.

Specifically, how does using apply affect the number of steps the program takes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

val list = mutableListOf()
val n = 1000
val result = list.apply {
    for (i in 1..n) {
        add(i)
    }
}
println(result.size)
    

This code uses apply to add numbers from 1 to n into a list, then prints the list size.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for loop that adds elements to the list.
• How many times: Exactly n times, once for each number from 1 to n.

How Execution Grows With Input

Each time we increase n, the loop runs that many more times, adding one element per run.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The number of steps grows directly with the size of n. Double n, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the code grows in a straight line with the number of items added.

Common Mistake

[X] Wrong: "Using apply makes the code run faster because it's a special function."

[OK] Correct: apply just helps organize code; it doesn't change how many times the loop runs or how much work is done.

Interview Connect

Understanding how helper functions like apply affect time helps you explain your code clearly and shows you know what really costs time in programs.

Self-Check

"What if we replaced the for loop inside apply with a call to repeat(n)? How would the time complexity change?"

Practice

1. What does the apply function do in Kotlin?

easy

A. Runs code on an object and returns the same object

B. Creates a new object and returns it

C. Runs code and returns the last expression result

D. Runs code without returning anything

Solution

1. Step 1: Understand the purpose of apply

   The apply function executes a block of code on the object it is called on.

2. Step 2: Identify the return value of apply

   It always returns the original object after applying the block, not a new value.

3. Final Answer:

   Runs code on an object and returns the same object -> Option A

4. Quick Check:

   apply returns the object itself [OK]

Hint: Remember: apply returns the original object after changes [OK]

Common Mistakes:

• Thinking apply returns the last expression result
• Confusing apply with let or run
• Assuming apply creates a new object

2. Which of the following is the correct syntax to use apply on an object person to set its name property to "Alice"?

easy

A. person.apply { name = "Alice" }

B. apply(person) { name = "Alice" }

C. person.apply(name = "Alice")

D. person.apply { setName("Alice") }

Solution

1. Step 1: Identify the correct lambda syntax for apply

   apply takes a lambda with receiver where this is the object, so properties can be set directly.

2. Step 2: Check each option's syntax

   person.apply { name = "Alice" } correctly uses person.apply { name = "Alice" }. apply(person) { name = "Alice" } is invalid syntax. person.apply(name = "Alice") wrongly passes a parameter. person.apply { setName("Alice") } assumes a setter method which may not exist.

3. Final Answer:

   person.apply { name = "Alice" } -> Option A

4. Quick Check:

   Use object.apply { property = value } syntax [OK]

Hint: Use curly braces with apply to set properties inside [OK]

Common Mistakes:

• Passing parameters directly to apply
• Using parentheses instead of curly braces
• Calling non-existent setter methods

3. What is the output of this Kotlin code?

val list = mutableListOf<Int>().apply {
    add(1)
    add(2)
    add(3)
}
println(list)

medium

A. Compilation error

B. []

C. null

D. [1, 2, 3]

Solution

1. Step 1: Understand what apply does on the list

   The apply block adds 1, 2, and 3 to the mutable list.

2. Step 2: Check the returned value of apply

   apply returns the original list after adding the elements, so list contains [1, 2, 3].

3. Final Answer:

   [1, 2, 3] -> Option D

4. Quick Check:

   apply adds elements and returns the list [OK]

Hint: apply returns the object after running code inside [OK]

Common Mistakes:

• Expecting apply to return last added element
• Thinking list is empty after apply
• Confusing apply with run or let

4. Identify the error in this Kotlin code using apply:

val map = mutableMapOf()
map.apply {
    put("a", 1)
    put("b", 2)
}
println(map.get("c"))

medium

A. Syntax error in apply block

B. Compilation error due to missing return

C. No error; output is null

D. Runtime error: key "c" not found

Solution

1. Step 1: Check the apply block usage

   The apply block correctly adds two entries to the map.

2. Step 2: Understand the map.get("c") call

   Since key "c" does not exist, get returns null, which is printed without error.

3. Final Answer:

   No error; output is null -> Option C

4. Quick Check:

   Accessing missing key returns null, no error [OK]

Hint: Missing keys in map.get return null, no crash [OK]

Common Mistakes:

• Expecting runtime error for missing key
• Thinking apply must return a value explicitly
• Confusing map access syntax

5. You want to create and configure a StringBuilder in Kotlin to build the string "Hello World!" using apply. Which code snippet correctly does this?

hard

A. val result = StringBuilder().apply { append("Hello"); append(" World!") }

B. val result = StringBuilder().apply { append("Hello"); append(" World!") }.toString()

C. val result = StringBuilder().apply { append("Hello World!") }

D. val result = StringBuilder().apply { append("Hello"); append(" World!") }.toString

Solution

1. Step 1: Understand apply returns the object itself

   The apply block configures the StringBuilder, but to get the string, toString() must be called after.

2. Step 2: Check each option's correctness

   val result = StringBuilder().apply { append("Hello"); append(" World!") }.toString() calls toString() after apply, returning the built string. val result = StringBuilder().apply { append("Hello World!") } returns the StringBuilder object, not the string. val result = StringBuilder().apply { append("Hello"); append(" World!") } misses toString(). val result = StringBuilder().apply { append("Hello"); append(" World!") }.toString misses parentheses on toString, causing error.

3. Final Answer:

   val result = StringBuilder().apply { append("Hello"); append(" World!") }.toString() -> Option B

4. Quick Check:

   Call toString() after apply to get string [OK]

Hint: Call toString() after apply to get final string [OK]

Common Mistakes:

• Forgetting to call toString() after apply
• Missing parentheses on toString
• Expecting apply to return string automatically