Capture lists in closures in Swift - Time & Space Complexity

Time Complexity: Capture lists in closures

O(n)

Understanding Time Complexity

When using capture lists in closures, it is important to understand how the closure accesses variables and how often it runs. This helps us see how the program's work grows as input changes.

We want to know how the closure's execution time changes with the size of captured data or repeated calls.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    func makeIncrementer(amount: Int) -> () -> Int {
        var total = 0
        return { [amount] in
            total += amount
            return total
        }
    }
    
    let incrementByFive = makeIncrementer(amount: 5)
    print(incrementByFive())
    print(incrementByFive())
    

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

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The closure increments a variable and returns it each time it is called.
• How many times: Each call to the closure runs the increment operation once.

How Execution Grows With Input

The closure runs a simple addition each time it is called, regardless of input size.

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

Pattern observation: The work grows directly with the number of times the closure is called, one addition per call.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows linearly with the number of closure calls.

Common Mistake

[X] Wrong: "The capture list makes the closure run faster or slower depending on the size of captured variables."

[OK] Correct: The capture list only controls how variables are captured, not how many times the closure runs or how much work each call does.

Interview Connect

Understanding how closures capture variables and how that affects repeated execution helps you reason about performance in real Swift code. This skill shows you can think about both code behavior and efficiency.

Self-Check

What if the closure captured a large array instead of a single integer? How would the time complexity change when calling the closure multiple times?

Practice

1. What is the main purpose of using a capture list in a Swift closure?

easy

A. To control how variables are stored and referenced inside the closure

B. To define the return type of the closure

C. To specify the closure's parameter types

D. To make the closure run asynchronously

Solution

1. Step 1: Understand what capture lists do

   Capture lists let you specify how variables are captured inside closures, either by strong, weak, or unowned references.

2. Step 2: Identify the main purpose

   The main purpose is to control how variables are stored and referenced to avoid memory leaks or unexpected behavior.

3. Final Answer:

   To control how variables are stored and referenced inside the closure -> Option A

4. Quick Check:

   Capture list purpose = control variable capture [OK]

Hint: Capture lists manage variable references inside closures [OK]

Common Mistakes:

• Confusing capture lists with closure parameters
• Thinking capture lists define return types
• Assuming capture lists affect closure execution timing

2. Which of the following is the correct syntax to declare a capture list with a weak reference to self in a Swift closure?

easy

A. let closure = { [self weak] in print(self) }

B. let closure = { weak self in print(self) }

C. let closure = { [weak self] in print(self) }

D. let closure = { (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

   let closure = { [weak self] in print(self) } uses the correct syntax: [weak self] inside square brackets before the closure body.

3. Final Answer:

   let closure = { [weak self] in print(self) } -> Option C

4. Quick Check:

   Capture list syntax = [weak self] [OK]

Hint: Capture lists go inside square brackets before closure body [OK]

Common Mistakes:

• Omitting square brackets around capture list
• Placing 'weak' outside the brackets
• Using parentheses instead of brackets

3. What will be the output of the following Swift code?

class Example {
    var value = 10
    lazy var closure: () -> Void = { [unowned self] in
        print(self.value)
    }
}
let example = Example()
example.value = 20
example.closure()

medium

A. 20

B. 10

C. Runtime error

D. nil

Solution

1. Step 1: Understand unowned self capture

   The closure captures self as unowned, meaning it references the original object without increasing retain count.

2. Step 2: Check value at closure call

   example.value is updated to 20 before calling closure, so print(self.value) outputs 20.

3. Final Answer:

   20 -> Option A

4. Quick Check:

   Unowned self captures current value = 20 [OK]

Hint: Unowned self captures current object state, not copy [OK]

Common Mistakes:

• Thinking closure captures old value copy
• Confusing unowned with weak causing nil
• Expecting runtime error without object deallocation

4. Identify the error in this Swift closure using a capture list:

class Test {
    var count = 0
    lazy var closure: () -> Void = { [weak self] in
        self.count += 1
        print(self.count)
    }
}

medium

A. No error, code is correct

B. Capture list syntax is incorrect

C. Closure cannot be lazy with capture list

D. Cannot use weak self without unwrapping optional

Solution

1. Step 1: Analyze weak self usage

   When capturing self as weak, self becomes an optional inside the closure.

2. Step 2: Check code for optional unwrapping

   The code uses self.count directly without unwrapping, causing a compile error.

3. Final Answer:

   Cannot use weak self without unwrapping optional -> Option D

4. Quick Check:

   Weak self requires optional unwrapping [OK]

Hint: Weak self is optional; unwrap before use [OK]

Common Mistakes:

• Using weak self as non-optional
• Ignoring optional chaining or guard let
• Assuming lazy closures can't have capture lists

5. You want to create a closure that captures a variable by making a copy of it, so changes outside the closure don't affect the closure's value. Which capture list syntax should you use in Swift?

hard

A. [weak variable]

B. [value = variable]

C. [unowned variable]

D. [copy variable]

Solution

1. Step 1: Understand capture by copy

   To capture a variable by making a copy, you assign it inside the capture list using syntax like [value = variable].

2. Step 2: Evaluate options

   [value = variable] uses the correct syntax to copy the variable's value into the closure's capture list.

3. Final Answer:

   [value = variable] -> Option B

4. Quick Check:

   Copy capture syntax = [value = variable] [OK]

Hint: Use [newName = oldVar] to capture a copy [OK]

Common Mistakes:

• Using weak or unowned which capture references
• Assuming [copy variable] is valid syntax
• Not assigning variable inside capture list