Unowned references for guaranteed lifetime in Swift - Step-by-Step Execution

Concept Flow - Unowned references for guaranteed lifetime

Create Object A

↓

Create Object B

↓

Assign unowned reference from B to A

↓

Use unowned reference

↓

Objects deallocate safely

↓

No strong reference cycle

This flow shows creating two objects where one holds an unowned reference to the other, ensuring no strong cycle and safe deallocation.

Execution Sample

Swift

class Owner {
    var pet: Pet?
}

class Pet {
    unowned let owner: Owner
    init(owner: Owner) { self.owner = owner }
}

let owner = Owner()
owner.pet = Pet(owner: owner)

This code creates an Owner and a Pet where Pet holds an unowned reference to Owner, avoiding strong reference cycles.

Execution Table

Step	Action	Variable States	Reference Types	Notes
1	Create Owner instance	owner: Owner instance	Strong reference to Owner	Owner object created in memory
2	Create Pet instance with unowned owner	pet: Pet instance, pet.owner unowned reference to owner	Strong reference to Pet, unowned reference from Pet to Owner	Pet holds unowned reference to Owner
3	Assign pet to owner.pet	owner.pet points to pet	Strong reference from owner to pet	Owner strongly owns Pet
4	Use pet.owner	Access pet.owner	Unowned reference access	Safe access because owner exists
5	Deallocate owner and pet	owner and pet deallocated	No strong reference cycle	Objects deallocate safely

💡 Execution stops after objects deallocate safely with no memory leaks due to unowned reference.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5
owner	nil	Owner instance	Owner instance	Owner instance	nil (deallocated)
pet	nil	nil	Pet instance	Pet instance	nil (deallocated)
pet.owner (unowned)	nil	nil	Points to owner	Points to owner	nil (deallocated)

Key Moments - 3 Insights

Why is pet.owner declared as unowned instead of strong?

Because owner already strongly owns pet, making pet.owner unowned avoids a strong reference cycle, as shown in execution_table step 2 and 3.

What happens if owner is deallocated before pet?

Accessing pet.owner would cause a runtime error because unowned references assume the referenced object exists, so owner must outlive pet (see execution_table step 5).

Why is it safe to access pet.owner without optional unwrapping?

Because unowned references guarantee the referenced object exists during pet's lifetime, so no need for optional checks (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the unowned reference from pet to owner established?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Reference Types' column in execution_table rows to see when pet.owner is assigned.

According to variable_tracker, what is the state of 'owner' after step 5?

A Owner is unowned

B Owner instance still exists

C Owner is nil (deallocated)

D Owner is strongly referenced by pet

💡 Hint

Look at the 'owner' row in variable_tracker under 'After Step 5'.

If pet.owner was a strong reference instead of unowned, what would happen?

A Strong reference cycle causing memory leak

B Pet would deallocate before owner

C No change in memory management

D Owner would be nil immediately

💡 Hint

Refer to key_moments about strong reference cycles and execution_table steps 2 and 3.

Concept Snapshot

Unowned references hold a non-owning link to another object.
They avoid strong reference cycles when one object must outlive the other.
Use unowned when the referenced object is guaranteed to exist.
Accessing unowned references is safe without optionals.
If the referenced object is deallocated first, accessing unowned causes a crash.

Full Transcript

This visual execution traces how unowned references work in Swift to avoid strong reference cycles. First, an Owner object is created with a strong reference. Then a Pet object is created with an unowned reference back to the Owner. The Owner strongly owns the Pet, but the Pet only holds an unowned reference to the Owner. This setup prevents a memory leak. The execution table shows each step: creation, assignment, usage, and deallocation. The variable tracker shows how variables change over time. Key moments clarify why unowned is used and the importance of object lifetimes. The quiz tests understanding of when references are set and the consequences of using strong instead of unowned references. The snapshot summarizes the key points about unowned references and their safe use in Swift.