Suspend functions concept in Kotlin - Time & Space Complexity
We want to understand how the time it takes to run suspend functions changes as the input grows.
How does the program's work increase when using suspend functions with more data?
Analyze the time complexity of the following code snippet.
suspend fun fetchData(ids: List<Int>): List<String> {
val results = mutableListOf<String>()
for (id in ids) {
val data = fetchFromNetwork(id) // suspend function
results.add(data)
}
return results
}
suspend fun fetchFromNetwork(id: Int): String {
// Simulate network delay
kotlinx.coroutines.delay(100)
return "Data for $id"
}
This code fetches data for each id in a list by calling a suspend function that simulates a network delay.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Looping over the list of ids and calling the suspend function fetchFromNetwork for each.
- How many times: Once for each id in the input list.
Each new id adds one more network call, so the total work grows directly with the number of ids.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 network calls |
| 100 | 100 network calls |
| 1000 | 1000 network calls |
Pattern observation: The work grows in a straight line as the input size increases.
Time Complexity: O(n)
This means the time to finish grows directly in proportion to the number of items we process.
[X] Wrong: "Suspend functions run all at once, so time stays the same no matter how many items."
[OK] Correct: Each suspend call waits for its own delay before continuing, so doing many calls one after another adds up time.
Understanding how suspend functions affect time helps you explain how asynchronous code scales in real apps.
"What if we changed the for-loop to run all fetchFromNetwork calls concurrently? How would the time complexity change?"
Practice
suspend function in Kotlin?Solution
Step 1: Understand what suspend functions do
Suspend functions let the program pause execution at some point and resume later without blocking the thread.Step 2: Compare options with this behavior
Only To allow the function to pause and resume without blocking the thread describes this pausing and resuming behavior correctly.Final Answer:
To allow the function to pause and resume without blocking the thread -> Option CQuick Check:
Suspend function purpose = pause and resume without blocking [OK]
- Thinking suspend means multithreading
- Confusing suspend with deprecated functions
- Assuming suspend converts functions to lambdas
Solution
Step 1: Recall suspend function syntax
The correct syntax places thesuspendkeyword beforefun.Step 2: Check each option
Only suspend fun fetchData() { } matches the correct syntax:suspend fun fetchData() { }.Final Answer:
suspend fun fetchData() { } -> Option DQuick Check:
Suspend function syntax = suspend before fun [OK]
- Placing suspend after fun
- Putting suspend after function name
- Mixing order of keywords
import kotlinx.coroutines.*
suspend fun greet() {
delay(100)
println("Hello from suspend")
}
fun main() = runBlocking {
greet()
println("Done")
}Solution
Step 1: Understand runBlocking and suspend call
runBlocking starts a coroutine and allows calling suspend functions like greet().Step 2: Trace execution order
greet() delays 100ms, then prints "Hello from suspend". After greet() finishes, main prints "Done".Final Answer:
Hello from suspend\nDone -> Option AQuick Check:
Output order = greet() then Done [OK]
- Assuming greet() runs asynchronously and prints after Done
- Thinking delay causes errors outside coroutine
- Confusing suspend function calls outside coroutines
fun fetchData() {
delay(1000)
println("Data fetched")
}Solution
Step 1: Check usage of delay()
delay() is a suspend function and can only be called from suspend functions or coroutines.Step 2: Analyze fetchData() declaration
fetchData() is a regular function without suspend keyword, so calling delay() inside causes an error.Final Answer:
delay() cannot be called from a non-suspend function -> Option AQuick Check:
delay() call requires suspend function context [OK]
- Thinking delay() works in normal functions
- Believing println() is restricted
- Confusing delay() argument type
fetchUserData() that calls another suspend function fetchFromNetwork() and returns its result. Which of the following is the correct way to implement fetchUserData()?Solution
Step 1: Recognize suspend function chaining rules
A suspend function calling another suspend function must itself be marked suspend.Step 2: Check each option's syntax and behavior
suspend fun fetchUserData() = fetchFromNetwork() correctly declares fetchUserData() as suspend and returns fetchFromNetwork() result. The option with suspend fun fetchUserData() { fetchFromNetwork() } misses returning the result. The remaining options have incorrect syntax.Final Answer:
suspend fun fetchUserData() = fetchFromNetwork() -> Option BQuick Check:
Calling suspend inside suspend requires suspend keyword [OK]
- Omitting suspend keyword on calling function
- Using wrong suspend syntax order
- Not returning the result from called suspend function
Ready to prove it?
Pass the test and this pattern moves unknown
