Closures are reference types in Swift - Time & Space Complexity

Time Complexity: Closures are reference types

O(n)

Understanding Time Complexity

When working with closures in Swift, it's important to understand how their reference nature affects performance.

We want to see how the cost of using closures grows as we create or call more of them.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    func makeIncrementer(amount: Int) -> () -> Int {
        var total = 0
        let incrementer: () -> Int = {
            total += amount
            return total
        }
        return incrementer
    }

    let incrementByTen = makeIncrementer(amount: 10)
    for _ in 1...n {
        _ = incrementByTen()
    }
    

This code creates a closure that adds a fixed amount each time it is called, then calls it n times.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Calling the closure inside the loop.
• How many times: The closure is called n times, once per loop iteration.

How Execution Grows With Input

Each time we call the closure, it performs a simple addition and returns a value.

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

Pattern observation: The number of operations grows directly with n, the number of times the closure is called.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as we call the closure more times.

Common Mistake

[X] Wrong: "Closures are simple values, so calling them many times is always constant time."

[OK] Correct: Each closure call runs code, so calling it n times means n operations, not just one.

Interview Connect

Understanding how closures behave as reference types helps you reason about performance and memory in real apps.

Self-Check

What if we created a new closure inside the loop each time instead of calling the same one? How would the time complexity change?

Practice

1. What does it mean when we say closures are reference types in Swift?

easy

A. Multiple variables can point to the same closure instance, sharing changes.

B. Closures cannot capture variables from their surrounding context.

C. Each time you assign a closure, a new copy is created.

D. Closures are stored only as values, not references.

Solution

1. Step 1: Understand what reference types mean

   Reference types mean multiple variables can point to the same instance in memory.

2. Step 2: Apply this to closures

   Since closures are reference types, assigning them copies the reference, not the code itself.

3. Final Answer:

   Multiple variables can point to the same closure instance, sharing changes. -> Option A

4. Quick Check:

   Closures share instance references [OK]

Hint: Reference types share instances, not copies [OK]

Common Mistakes:

• Thinking closures always create new copies
• Confusing closures with value types like structs
• Ignoring that closures capture variables by reference

2. Which of the following is the correct way to assign a closure to a variable in Swift?

easy

A. func closure = { print("Hello") }

B. let closure = { print("Hello") }

C. closure := { print("Hello") }

D. var closure = function printHello() {}

Solution

1. Step 1: Recall Swift closure syntax

   Closures are assigned using curly braces and can be stored in variables with let or var.

2. Step 2: Check each option

   let closure = { print("Hello") } uses correct syntax: let closure = { print("Hello") }.

3. Final Answer:

   let closure = { print("Hello") } -> Option B

4. Quick Check:

   Correct closure assignment syntax [OK]

Hint: Closures use curly braces and assign with let or var [OK]

Common Mistakes:

• Using := which is not Swift syntax
• Trying to declare closures like functions
• Using func keyword incorrectly for closures

3. What will be printed by this Swift code?

var closureA = { print("Count: 0") }
var closureB = closureA
closureA = { print("Count: 1") }
closureB()

medium

A. Count: 0

B. Count: 1

C. No output, error occurs

D. Count: 0 and Count: 1

Solution

1. Step 1: Understand closure assignment

   closureB is assigned closureA's original closure printing "Count: 0".

2. Step 2: Reassign closureA

   closureA is changed to a new closure printing "Count: 1", but closureB still points to the old closure.

3. Final Answer:

   Count: 0 -> Option A

4. Quick Check:

   closureB keeps original closure [OK]

Hint: Reassigning closureA doesn't change closureB's reference [OK]

Common Mistakes:

• Assuming closureB changes when closureA is reassigned
• Confusing closure references with copies
• Expecting both closures to print the same after reassignment

4. Identify the error in this Swift code involving closures:

var closure1 = { print("Hello") }
var closure2 = closure1
closure1 = { print("World") }
closure2 = closure1

medium

A. Closure syntax is invalid

B. Cannot assign closure1 to closure2 after reassignment

C. No error, code runs fine

D. Variables closure1 and closure2 must be constants

Solution

1. Step 1: Check closure assignments

   Both closure1 and closure2 are variables and can be reassigned closures.

2. Step 2: Validate syntax and assignments

   All closure assignments use correct syntax and valid variable usage.

3. Final Answer:

   No error, code runs fine -> Option C

4. Quick Check:

   Valid closure reassignment [OK]

Hint: Variables can be reassigned closures freely [OK]

Common Mistakes:

• Thinking reassignment causes errors
• Confusing closure syntax with function syntax
• Assuming closures must be constants

5. Given this Swift code, what will be printed?

func makeCounter() -> () -> Int {
    var count = 0
    let increment: () -> Int = {
        count += 1
        return count
    }
    return increment
}

let counter1 = makeCounter()
let counter2 = counter1
print(counter1())
print(counter2())

hard

A. 1 and 1

B. 0 and 1

C. 2 and 2

D. 1 and 2

Solution

1. Step 1: Understand closure capturing

   The closure increments and returns the same captured variable 'count'.

2. Step 2: Analyze reference sharing

   counter1 and counter2 reference the same closure instance, so increments affect both.

3. Step 3: Trace calls

   First call counter1() returns 1, second call counter2() increments count to 2 and returns 2.

4. Final Answer:

   1 and 2 -> Option D

5. Quick Check:

   Shared closure state increments count [OK]

Hint: Closures share captured variables and state [OK]

Common Mistakes:

• Thinking counter2 is independent copy
• Ignoring closure captures and shared state
• Assuming count resets on each call