Memory implications of captures in Swift - Time & Space Complexity

Time Complexity: Memory implications of captures

O(n)

Understanding Time Complexity

When a Swift closure captures variables, it can affect how much memory the program uses over time.

We want to see how the memory use grows as the closure captures more data or runs more times.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

func makeIncrementer() -> () -> Int {
    var total = 0
    return {
        total += 1
        return total
    }
}

let increment = makeIncrementer()
print(increment())
print(increment())
    

This code creates a closure that captures a variable and updates it each time the closure runs.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The closure increments and returns the captured variable total.
• How many times: Each time the closure is called, it updates total once.

How Execution Grows With Input

Each call to the closure does a simple addition and returns a value, so the work per call stays the same.

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

Pattern observation: The number of operations grows directly with how many times the closure runs.

Final Time Complexity

Time Complexity: O(n)

This means if you call the closure n times, the total work grows in a straight line with n.

Common Mistake

[X] Wrong: "The closure captures the variable once, so calling it many times doesn't add any cost."

[OK] Correct: Each call still does work to update and return the variable, so the total work grows with calls.

Interview Connect

Understanding how closures capture variables and how that affects memory and work helps you write clear and efficient Swift code.

Self-Check

"What if the closure captured a large array and appended to it each time? How would the time complexity change?"

Practice

1. What happens when a Swift closure captures a variable strongly by default?

easy

A. The closure keeps a strong reference, potentially causing memory leaks if not handled.

B. The variable is copied and changes inside the closure do not affect the original.

C. The closure does not keep any reference to the variable.

D. The variable is automatically released when the closure is created.

Solution

1. Step 1: Understand default capture behavior

   By default, Swift closures capture variables strongly, meaning they keep a reference to the original variable.

2. Step 2: Recognize memory implications

   If the closure and the captured variable reference each other, it can cause a retain cycle, leading to memory leaks.

3. Final Answer:

   The closure keeps a strong reference, potentially causing memory leaks if not handled. -> Option A

4. Quick Check:

   Strong capture = possible memory leak [OK]

Hint: Strong capture keeps variables alive, watch for retain cycles [OK]

Common Mistakes:

• Thinking variables are copied by default
• Assuming closures do not hold references
• Believing variables auto-release on capture

2. Which syntax correctly declares a capture list to weakly capture a variable self in a Swift closure?

easy

A. { (weak self) in print(self) }

B. { self weak in print(self) }

C. { weak self -> Void in print(self) }

D. { [weak self] in print(self) }

Solution

1. Step 1: Recall capture list syntax

   Capture lists are declared inside square brackets before the closure parameters, e.g., [weak self].

2. Step 2: Match correct syntax

   { [weak self] in print(self) } uses the correct syntax: { [weak self] in ... }.

3. Final Answer:

   { [weak self] in print(self) } -> Option D

4. Quick Check:

   Capture list uses square brackets [weak self] [OK]

Hint: Capture lists use square brackets before closure parameters [OK]

Common Mistakes:

• Using parentheses instead of square brackets
• Placing 'weak' outside capture list
• Incorrect arrow syntax in capture list

3. What will be printed by the following Swift code?

class Person {
    var name = "Alice"
    lazy var greet: () -> Void = { [unowned self] in
        print("Hello, \(self.name)!")
    }
}
let p = Person()
p.greet()

medium

A. Hello, !

B. Hello, Optional("Alice")!

C. Hello, Alice!

D. Runtime error due to unowned reference

Solution

1. Step 1: Analyze closure capture

   The closure captures self as unowned, meaning it expects self to always exist when called.

2. Step 2: Check code execution

   Instance p is created, greet closure is called, printing "Hello, Alice!" using self.name.

3. Final Answer:

   Hello, Alice! -> Option C

4. Quick Check:

   Unowned capture prints value safely if object exists [OK]

Hint: Unowned captures assume object exists, no optional needed [OK]

Common Mistakes:

• Expecting Optional wrapping in output
• Thinking unowned causes runtime error immediately
• Assuming empty string prints

4. Identify the problem in this Swift code snippet and how to fix it:

class ViewController {
    var title = "Main"
    lazy var printTitle = {
        print(self.title)
    }
}
let vc = ViewController()
vc.printTitle()

medium

A. No problem, code runs fine and prints "Main".

B. Retain cycle due to strong self capture; fix with [weak self] capture list.

C. Syntax error: missing capture list brackets.

D. Runtime error: self is nil inside closure.

Solution

1. Step 1: Identify capture type

   The closure captures self strongly by default, which can cause retain cycles if ViewController holds the closure.

2. Step 2: Fix with weak capture

   Adding [weak self] in the capture list prevents retain cycle by capturing self weakly.

3. Final Answer:

   Retain cycle due to strong self capture; fix with [weak self] capture list. -> Option B

4. Quick Check:

   Strong capture in closures can cause retain cycles [OK]

Hint: Use [weak self] to avoid retain cycles in closures [OK]

Common Mistakes:

• Ignoring retain cycles in lazy properties
• Assuming no capture means no memory issues
• Confusing syntax errors with memory issues

5. You have a Swift class with a closure property that captures a variable data. You want to ensure the closure does not keep data alive if the class instance is deallocated, but still access data safely inside the closure. Which capture strategy should you use?

hard

A. Capture data weakly and unwrap it safely inside the closure.

B. Capture data unowned without checks inside the closure.

C. Capture data strongly to keep it alive as long as the closure exists.

D. Do not capture data at all; pass it as a parameter instead.

Solution

1. Step 1: Understand capture effects on memory

   Strong capture keeps data alive, which may cause memory leaks if the class is deallocated.

2. Step 2: Choose safe capture method

   Weak capture allows data to be nil if deallocated; unwrapping safely avoids crashes.

3. Step 3: Compare with unowned and no capture

   Unowned assumes data always exists, risking crashes. Not capturing requires passing data every time, which may be inconvenient.

4. Final Answer:

   Capture data weakly and unwrap it safely inside the closure. -> Option A

5. Quick Check:

   Weak capture + safe unwrap = safe memory handling [OK]

Hint: Use weak capture and optional unwrap for safe memory use [OK]

Common Mistakes:

• Using unowned and risking runtime crashes
• Strong capture causing retain cycles
• Ignoring safe unwrapping of weak references