Weak self and unowned self patterns in Swift

Introduction

These patterns help avoid memory problems when objects refer to each other. They keep your app running smoothly without crashes.

When you have two objects that refer to each other and want to avoid memory leaks.

When using closures that capture self inside a class to prevent strong reference cycles.

When you want to safely access self inside a closure without keeping it alive forever.

When you know self will always exist while the closure runs and want to avoid optional unwrapping.

When you want to prevent your app from crashing due to unexpected nil values in closures.

Syntax

Swift

someClosure = { [weak self] in
    guard let self = self else { return }
    // use self safely here
}

someClosure = { [unowned self] in
    // use self directly here
}

weak self creates a temporary, optional reference to self that can become nil.

unowned self creates a non-optional reference but assumes self will never be nil.

Examples

This example uses weak self to avoid a strong reference cycle. It safely unwraps self before use.

Swift

class Example {
    var closure: (() -> Void)?
    func setup() {
        closure = { [weak self] in
            guard let self = self else { return }
            print("Using weak self safely")
        }
    }
}

This example uses unowned self assuming self will always exist when the closure runs.

Swift

class Example {
    var closure: (() -> Void)?
    func setup() {
        closure = { [unowned self] in
            print("Using unowned self directly")
        }
    }
}

Sample Program

This program shows how weak self safely handles the case when the object is gone, while unowned self assumes the object is still there.

Swift

class Person {
    let name: String
    var greeting: (() -> Void)?

    init(name: String) {
        self.name = name
    }

    func greetWeak() {
        greeting = { [weak self] in
            guard let self = self else {
                print("Person no longer exists")
                return
            }
            print("Hello, my name is \(self.name) using weak self")
        }
    }

    func greetUnowned() {
        greeting = { [unowned self] in
            print("Hello, my name is \(self.name) using unowned self")
        }
    }
}

var person: Person? = Person(name: "Alice")
person?.greetWeak()
person?.greeting?()
person = nil

var person2: Person? = Person(name: "Bob")
person2?.greetUnowned()
person2?.greeting?()
person2 = nil

Important Notes

Use weak self when self might become nil and you want to avoid crashes.

Use unowned self only when you are sure self will not be nil during closure execution.

Always test your code to avoid unexpected nil errors or memory leaks.

Summary

Weak self helps avoid memory leaks by allowing self to become nil inside closures.

Unowned self assumes self will always exist and avoids optional unwrapping.

Choosing the right pattern keeps your app safe and efficient.

Practice

1. What is the main reason to use weak self inside a closure in Swift?

easy

A. To make self immutable inside the closure

B. To guarantee self will never be nil inside the closure

C. To prevent strong reference cycles and allow self to become nil

D. To create a copy of self for thread safety

Solution

1. Step 1: Understand strong reference cycles

   Strong reference cycles happen when closures capture self strongly, causing memory leaks.

2. Step 2: Role of weak self

   Using weak self makes the reference to self optional and allows it to become nil, breaking the cycle.

3. Final Answer:

   To prevent strong reference cycles and allow self to become nil -> Option C

4. Quick Check:

   Weak self avoids memory leaks = A [OK]

Hint: Weak self means self can be nil inside closures [OK]

Common Mistakes:

• Thinking weak self guarantees non-nil self
• Confusing weak with unowned self
• Assuming weak self copies self

2. Which of the following is the correct syntax to capture self as unowned in a Swift closure?

easy

A. [weak self] in

B. [unowned self] in

C. [self unowned] in

D. [unowned] self in

Solution

1. Step 1: Recall capture list syntax

   Swift uses square brackets with capture specifiers before in in closures.

2. Step 2: Correct unowned syntax

   The correct syntax is [unowned self] in to capture self as unowned.

3. Final Answer:

   [unowned self] in -> Option B

4. Quick Check:

   Unowned capture syntax = [unowned self] in [OK]

Hint: Capture lists use square brackets with 'unowned self' [OK]

Common Mistakes:

• Swapping order like [self unowned]
• Missing brackets or 'in' keyword
• Using weak instead of unowned when asked

3. Consider this Swift code snippet:

class Example {
    var closure: (() -> Void)?
    func setup() {
        closure = { [weak self] in
            print(self == nil ? "nil" : "not nil")
        }
    }
}
let example = Example()
example.setup()
example.closure?()

What will be printed when example.closure?() is called?

medium

A. not nil

B. Compilation error

C. nil

D. Runtime crash

Solution

1. Step 1: Analyze weak self capture

   The closure captures self weakly, so inside the closure self is optional.

2. Step 2: Check self lifetime

   The example instance is still alive when closure?() is called, so self is not nil.

3. Final Answer:

   not nil -> Option A

4. Quick Check:

   Weak self is alive here = not nil [OK]

Hint: If instance exists, weak self is not nil inside closure [OK]

Common Mistakes:

• Assuming weak self is always nil
• Confusing weak self with unowned self
• Expecting runtime crash due to optional

4. Identify the problem in this Swift code and choose the best fix:

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

medium

A. Make greet a regular function instead of closure

B. Use [weak self] in closure to avoid strong reference cycle

C. Use [unowned self] in closure to avoid strong reference cycle

D. No problem; code works fine

Solution

1. Step 1: Detect strong reference cycle risk

   The closure captures self strongly, and greet is lazy var, so cycle possible.

2. Step 2: Choose unowned self for non-optional self

   Since self will always exist when greet is called, unowned self is safe and avoids optional unwrapping.

3. Final Answer:

   Use [unowned self] in closure to avoid strong reference cycle -> Option A

4. Quick Check:

   Unowned self for guaranteed self = C [OK]

Hint: Use unowned self if self always exists in closure [OK]

Common Mistakes:

• Ignoring strong reference cycles
• Using weak self and forcing unwrap unnecessarily
• Thinking no problem exists

5. You have a Swift class that manages a network request with a closure callback. You want to avoid memory leaks but also avoid optional unwrapping inside the closure. Which pattern should you use and why? Choose the best explanation.

hard

A. Do not capture self at all to avoid any reference issues

B. Use weak self to avoid leaks and unwrap self safely inside closure

C. Use strong self to keep the instance alive during the closure execution

D. Use unowned self because self will outlive the closure, avoiding optionals

Solution

1. Step 1: Understand lifetime of self and closure

   If self will definitely exist while closure runs, unowned self is safe and avoids optionals.

2. Step 2: Compare weak vs unowned for this case

   weak self requires optional unwrapping, but unowned self assumes self exists, simplifying code and avoiding leaks.

3. Final Answer:

   Use unowned self because self will outlive the closure, avoiding optionals -> Option D

4. Quick Check:

   Unowned self for guaranteed lifetime = A [OK]

Hint: Use unowned if self guaranteed alive, else weak [OK]

Common Mistakes:

• Using weak self but not unwrapping safely
• Using strong self causing memory leaks
• Ignoring self capture causing leaks