ARC overview for memory management in Swift - Mini Project: Build & Apply

ARC overview for memory management

📖 Scenario: Imagine you are building a simple app that manages a list of books. Each book has a title and an author. You want to understand how Swift automatically manages memory for your objects using ARC (Automatic Reference Counting).

🎯 Goal: You will create a simple class for books, create instances, and observe how ARC manages memory by tracking when objects are created and destroyed.

📋 What You'll Learn

Create a class called Book with a title property

Add an initializer that prints when a Book is created

Add a deinitializer that prints when a Book is destroyed

Create a variable to hold a Book instance

Set the variable to nil to release the Book instance

💡 Why This Matters

🌍 Real World

Understanding ARC helps you write efficient Swift apps that use memory well and avoid crashes.

💼 Career

Memory management is a key skill for iOS developers to build stable and performant apps.

1

Create the Book class with a title property

Create a class called Book with a title property of type String. Add an initializer that takes a title parameter and assigns it to the property. Inside the initializer, add a print statement that says "Book titled 'title' is created".

Swift

# Create the Book class with a title property and initializer
# Your code here

Hint

Remember to use self.title = title inside the initializer to set the property.

2

Add a deinitializer to the Book class

Add a deinit method to the Book class that prints "Book titled 'title' is being destroyed" when the object is removed from memory.

Swift

class Book {
    let title: String
    init(title: String) {
        self.title = title
        print("Book titled '\(title)' is created")
    }
    // Add deinitializer here
    // Your code here
}

Hint

The deinit method runs automatically when the object is removed from memory.

3

Create a variable to hold a Book instance

Create a variable called myBook and assign it a new Book instance with the title "Swift Programming".

Swift

class Book {
    let title: String
    init(title: String) {
        self.title = title
        print("Book titled '\(title)' is created")
    }
    deinit {
        print("Book titled '\(title)' is being destroyed")
    }
}

// Create myBook variable and assign a Book instance
// Your code here

Hint

Use var myBook: Book? = Book(title: "Swift Programming") to create the variable.

4

Set the myBook variable to nil to release the instance

Set the variable myBook to nil to release the Book instance and trigger the deinitializer.

Swift

class Book {
    let title: String
    init(title: String) {
        self.title = title
        print("Book titled '\(title)' is created")
    }
    deinit {
        print("Book titled '\(title)' is being destroyed")
    }
}

var myBook: Book? = Book(title: "Swift Programming")

// Set myBook to nil below
// Your code here

Hint

Setting myBook to nil removes the last reference to the object, so ARC destroys it.

Practice

1. What does ARC stand for in Swift's memory management?

easy

A. Active Reference Control

B. Automatic Resource Control

C. Asynchronous Runtime Code

D. Automatic Reference Counting

Solution

1. Step 1: Understand the acronym ARC

   ARC in Swift stands for Automatic Reference Counting, which manages memory automatically.

2. Step 2: Eliminate incorrect options

   Other options do not match the correct term used in Swift memory management.

3. Final Answer:

   Automatic Reference Counting -> Option D

4. Quick Check:

   ARC = Automatic Reference Counting [OK]

Hint: Remember ARC counts references automatically [OK]

Common Mistakes:

• Confusing ARC with manual memory management
• Thinking ARC stands for resource control
• Mixing ARC with asynchronous code concepts

2. Which of the following is the correct way to declare a class in Swift that ARC will manage?

easy

A. struct Person {}

B. class Person {}

C. func Person() {}

D. var Person = {}

Solution

1. Step 1: Identify ARC-managed types

   ARC manages memory for class instances, so classes are declared with class.

2. Step 2: Check syntax correctness

   class Person {} is the correct syntax for a class in Swift.

3. Final Answer:

   class Person {} -> Option B

4. Quick Check:

   Class declaration = class Person {} [OK]

Hint: ARC manages classes, not structs or functions [OK]

Common Mistakes:

• Using struct instead of class for ARC examples
• Trying to declare a class with func or var
• Confusing function and class syntax

3. Consider the following Swift code:

class Dog {}
var dog1: Dog? = Dog()
var dog2 = dog1
 dog1 = nil
print(dog2 == nil)

What will be printed?

medium

A. true

B. Compile error

C. false

D. nil

Solution

1. Step 1: Analyze reference assignments

   dog1 is assigned a Dog instance, dog2 copies the reference from dog1, so both point to the same object.

2. Step 2: Effect of setting dog1 to nil

   Setting dog1 to nil removes one reference, but dog2 still holds the reference, so the object remains alive.

3. Step 3: Evaluate print statement

   dog2 is not nil, so dog2 == nil is false, so it prints false.

4. Final Answer:

   false -> Option C

5. Quick Check:

   dog2 still references object = false [OK]

Hint: Setting one reference nil doesn't free object if others exist [OK]

Common Mistakes:

• Assuming dog2 becomes nil when dog1 is nil
• Confusing reference assignment with copying object
• Expecting a compile error due to optional usage

4. What is the problem with this Swift code snippet related to ARC?

class Person {
  var friend: Person?
}

var alice: Person? = Person()
alice?.friend = alice
alice = nil

medium

A. Memory leak due to strong reference cycle

B. Compile error because of optional chaining

C. No problem, memory is freed correctly

D. Runtime crash due to nil assignment

Solution

1. Step 1: Identify reference cycle

   alice references a Person instance, and that instance's friend property points back to alice, creating a strong cycle.

2. Step 2: Effect on ARC

   Because both references are strong, ARC cannot free the Person instance even after alice is set to nil, causing a memory leak.

3. Final Answer:

   Memory leak due to strong reference cycle -> Option A

4. Quick Check:

   Strong cycle prevents deallocation = memory leak [OK]

Hint: Strong references pointing to each other cause leaks [OK]

Common Mistakes:

• Thinking optional chaining causes compile error
• Assuming ARC frees memory despite cycles
• Believing nil assignment crashes program

5. You want to avoid a strong reference cycle between two classes Owner and Pet. Which is the best way to declare the reference from Pet to Owner to prevent memory leaks?

hard

A. Declare the reference as weak var owner: Owner?

B. Declare the reference as var owner: Owner

C. Declare the reference as unowned var owner: Owner?

D. Declare the reference as let owner: Owner

Solution

1. Step 1: Understand strong vs weak references

   Strong references increase ARC count and can cause cycles; weak references do not increase ARC count.

2. Step 2: Choose weak reference to break cycle

   Declaring owner as weak var owner: Owner? allows ARC to free objects properly by not increasing reference count.

3. Final Answer:

   Declare the reference as weak var owner: Owner? -> Option A

4. Quick Check:

   Use weak to avoid strong reference cycles [OK]

Hint: Use weak references to break cycles safely [OK]

Common Mistakes:

• Using unowned incorrectly causing crashes
• Using strong references causing memory leaks
• Forgetting to make weak references optional