Elvis operator deep usage in Kotlin - Time & Space Complexity

Time Complexity: Elvis operator deep usage

O(n)

Understanding Time Complexity

We want to understand how using the Elvis operator affects the speed of code when it runs many times.

Specifically, how does the time to finish change as the input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

fun processList(items: List): List {
    return items.map { it ?: "default" }
}
    

This code replaces null values in a list with "default" using the Elvis operator.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The map function loops over each item in the list once.
• How many times: Exactly once for each item in the input list.

How Execution Grows With Input

As the list gets bigger, the code checks each item once, so the work grows steadily with the list size.

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

Pattern observation: The number of operations grows directly with the input size.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line as the list gets bigger.

Common Mistake

[X] Wrong: "Using the Elvis operator makes the code slower because it adds extra checks inside the loop."

[OK] Correct: The Elvis operator is just a simple check done once per item, so it does not add extra loops or nested work. The overall time still grows linearly.

Interview Connect

Understanding how simple operators like Elvis affect performance helps you explain your code choices clearly and confidently in interviews.

Self-Check

"What if we replaced the map with a nested loop that also uses the Elvis operator inside? How would the time complexity change?"

Practice

1.

What does the Elvis operator ?: do in Kotlin?

easy

A. Checks if two values are equal.

B. Returns the left value if it is not null; otherwise returns the right value.

C. Converts a value to a nullable type.

D. Throws an exception if the left value is null.

Solution

1. Step 1: Understand the Elvis operator purpose

   The Elvis operator ?: is used to provide a default value when the left side is null.

2. Step 2: Analyze the behavior

   If the left value is not null, it returns that value; otherwise, it returns the right value.

3. Final Answer:

   Returns the left value if it is not null; otherwise returns the right value. -> Option B

4. Quick Check:

   Elvis operator returns left if not null else right [OK]

Hint: Elvis operator picks left if not null, else right [OK]

Common Mistakes:

• Thinking it compares two values
• Assuming it throws exceptions
• Confusing it with null checks

2.

Which of the following is the correct syntax to use the Elvis operator in Kotlin?

val result = value1 ??: value2

easy

A. val result = value1 ?: value2

B. val result = value1 ? value2

C. val result = value1 :: value2

D. val result = value1 ?:: value2

Solution

1. Step 1: Identify the correct Elvis operator syntax

   The Elvis operator in Kotlin is written as ?: without spaces.

2. Step 2: Match the syntax with options

   val result = value1 ?: value2 uses ?: correctly, while others use invalid or incorrect symbols.

3. Final Answer:

   val result = value1 ?: value2 -> Option A

4. Quick Check:

   Elvis operator syntax is ?: [OK]

Hint: Elvis operator is always ?: with no spaces [OK]

Common Mistakes:

• Using single question mark ? instead of ?:
• Using double colon :: by mistake
• Adding extra colons or spaces

3.

What is the output of the following Kotlin code?

val a: String? = null
val b: String? = "Hello"
val c: String? = null

val result = a ?: b ?: c ?: "Default"
println(result)

medium

A. Hello

B. null

C. Default

D. Compilation error

Solution

1. Step 1: Evaluate the chained Elvis operators

   Variable a is null, so Elvis operator moves to b. b is "Hello", which is not null.

2. Step 2: Determine the final value

   Since b is not null, result is assigned "Hello" and the rest is ignored.

3. Final Answer:

   Hello -> Option A

4. Quick Check:

   Chained Elvis picks first non-null: Hello [OK]

Hint: Chained Elvis returns first non-null value [OK]

Common Mistakes:

• Assuming it returns null if first is null
• Ignoring chaining and picking last value
• Thinking it causes a compile error

4.

Identify the error in this Kotlin code snippet using the Elvis operator:

val x: String? = null
val y: String = x ?: null

medium

A. Elvis operator cannot be used with nullable types

B. No error, code is correct

C. Variable x should not be nullable

D. Cannot assign null to non-nullable type String

Solution

1. Step 1: Analyze variable types and assignment

   Variable y is declared as non-nullable String, but x ?: null can be null.

2. Step 2: Understand Kotlin's null safety rules

   Assigning null to a non-nullable type causes a compilation error.

3. Final Answer:

   Cannot assign null to non-nullable type String -> Option D

4. Quick Check:

   Non-nullable cannot hold null [OK]

Hint: Non-nullable vars cannot be assigned null [OK]

Common Mistakes:

• Thinking Elvis operator changes nullability
• Assuming nullable can be assigned to non-nullable
• Ignoring Kotlin's strict null safety

5.

Given the following Kotlin code, what will be the output?

fun getName(user: Map): String {
    return user["firstName"] ?: user["nickname"] ?: user["lastName"] ?: "Anonymous"
}

val user1 = mapOf("firstName" to null, "nickname" to null, "lastName" to "Smith")
println(getName(user1))

hard

A. Anonymous

B. Compilation error

C. Smith

D. null

Solution

1. Step 1: Evaluate the map values in order

   firstName and nickname are null, so Elvis operator moves to lastName, which is "Smith".

2. Step 2: Determine the returned value

   Since lastName is not null, the function returns "Smith".

3. Final Answer:

   Smith -> Option C

4. Quick Check:

   Elvis chain returns first non-null: Smith [OK]

Hint: Elvis chains pick first non-null map value [OK]

Common Mistakes:

• Assuming it returns Anonymous despite lastName present
• Confusing null with string "null"
• Thinking map access causes error