Nil coalescing operator deep usage in Swift - Time & Space Complexity

Time Complexity: Nil coalescing operator deep usage

O(n)

Understanding Time Complexity

We want to see how the time it takes to run code with the nil coalescing operator changes as input grows.

How does using this operator affect the speed when many values are involved?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

let values: [Int?] = [nil, 3, nil, 7, 10, nil]
var results: [Int] = []

for value in values {
    let number = value ?? 0
    results.append(number)
}
    

This code goes through a list of optional numbers and uses the nil coalescing operator to replace nil with zero, then saves the result.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each element in the array.
• How many times: Once for every item in the list.

How Execution Grows With Input

Each new item adds one more check and append operation.

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

Pattern observation: The work grows evenly as the list gets bigger, adding one step per item.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows directly with the number of items you check.

Common Mistake

[X] Wrong: "Using the nil coalescing operator makes the code run faster than looping through the array."

[OK] Correct: The operator itself is very fast, but you still have to look at each item once, so the total time depends on the list size, not just the operator.

Interview Connect

Understanding how simple operators like nil coalescing affect performance helps you write clear and efficient code, a skill valued in many coding challenges and real projects.

Self-Check

"What if we replaced the for-loop with a map function using the nil coalescing operator? How would the time complexity change?"

Practice

1. What does the nil coalescing operator ?? do in Swift?

easy

A. It returns the value of an optional if it is not nil, otherwise returns a default value.

B. It forces unwraps an optional and crashes if nil.

C. It converts a non-optional value into an optional.

D. It checks if two optionals are equal.

Solution

1. Step 1: Understand the purpose of the nil coalescing operator

   The operator ?? is used to provide a default value when an optional is nil.

2. Step 2: Compare with other options

   Options A, C, and D describe different behaviors unrelated to ??.

3. Final Answer:

   It returns the value of an optional if it is not nil, otherwise returns a default value. -> Option A

4. Quick Check:

   Nil coalescing operator = default value fallback [OK]

Hint: Remember: ?? means "use this if nil" [OK]

Common Mistakes:

• Confusing ?? with forced unwrapping (!)
• Thinking ?? converts types
• Assuming ?? compares optionals

2. Which of the following is the correct syntax to use the nil coalescing operator in Swift?

easy

A. let value = optionalValue ??? defaultValue

B. let value = optionalValue ?: defaultValue

C. let value = optionalValue ? defaultValue

D. let value = optionalValue ?? defaultValue

Solution

1. Step 1: Recall the correct syntax for nil coalescing

   The correct syntax uses two question marks: ?? between the optional and the default value.

2. Step 2: Eliminate incorrect options

   Options B, C, and D use invalid or incorrect operators.

3. Final Answer:

   let value = optionalValue ?? defaultValue -> Option D

4. Quick Check:

   Syntax for nil coalescing = ?? [OK]

Hint: Look for exactly two question marks ?? [OK]

Common Mistakes:

• Using ?: which is from other languages
• Using single ? instead of ??
• Adding extra question marks ???

3. What is the output of the following Swift code?

let a: Int? = nil
let b: Int? = 5
let c: Int? = nil
let result = a ?? b ?? c ?? 10
print(result)

medium

A. 5

B. 10

C. nil

D. Compilation error

Solution

1. Step 1: Evaluate the chained nil coalescing

   The expression a ?? b ?? c ?? 10 checks each optional from left to right and returns the first non-nil value.

2. Step 2: Check each optional's value

   a is nil, so move to b which is 5 (non-nil), so the result is 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   First non-nil value = 5 [OK]

Hint: Chain ?? to pick first non-nil value [OK]

Common Mistakes:

• Assuming nil is returned if first is nil
• Ignoring chaining order
• Thinking default 10 is always returned

4. Identify the error in this Swift code using nil coalescing:

let x: Int? = nil
let y: Int = 3
let z = x ?? y ?? 5
print(z)

medium

A. x must be non-optional

B. No error, code runs fine

C. y must be optional to use ??

D. Cannot use ?? with non-optional y

Solution

1. Step 1: Understand the types involved in nil coalescing

   The operator ?? requires the right side to be the same type as the optional or a non-optional fallback value.

2. Step 2: Analyze the expression x ?? y ?? 5

   Here, x is Int?, y is Int, but y ?? 5 is invalid because y is not optional, so you cannot use ?? on it.

3. Final Answer:

   Cannot use ?? with non-optional y -> Cannot use ?? with non-optional y

4. Quick Check:

   Right side of ?? must be optional or value [OK]

Hint: Right side of ?? must be optional or value, not non-optional with ?? [OK]

Common Mistakes:

• Using ?? on non-optional values
• Confusing optional and non-optional types
• Assuming ?? works like || operator

5. Given the following Swift code, what will be the value of finalValue?

func getValue() -> Int? { return nil }
let a: Int? = nil
let b: Int? = getValue()
let c: Int? = 7
let finalValue = a ?? b ?? c ?? 0

hard

A. nil

B. 0

C. 7

D. Compilation error

Solution

1. Step 1: Evaluate each optional in the chain

   a is nil, b is nil (from getValue()), c is 7 (non-nil).

2. Step 2: Apply nil coalescing operator

   The expression a ?? b ?? c ?? 0 returns the first non-nil value, which is 7.

3. Final Answer:

   7 -> Option C

4. Quick Check:

   First non-nil in chain = 7 [OK]

Hint: Chain ?? to find first non-nil, else default [OK]

Common Mistakes:

• Assuming function return nil means error
• Ignoring that c is non-nil
• Thinking default 0 is returned always