Actor isolation concept in Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is actor isolation in Swift concurrency?

Actor isolation means that the data and methods inside an actor can only be accessed safely from that actor's own context. This prevents data races by ensuring only one task accesses the actor's state at a time.

beginner

Why does Swift use actor isolation?

Swift uses actor isolation to protect mutable state from concurrent access. It ensures that only one piece of code can change or read the actor's data at a time, avoiding bugs caused by multiple tasks running together.

intermediate

How do you access an actor's isolated property from outside the actor?

You must use asynchronous calls (with await) to access an actor's isolated properties or methods from outside. This lets Swift schedule the access safely without causing data races.

intermediate

What happens if you try to access an actor's isolated property directly from outside without async/await?

Swift will give a compile-time error because direct access breaks actor isolation rules. You must use async/await to respect the actor's concurrency safety.

intermediate

Can an actor call its own isolated methods synchronously?

Yes, inside the actor's own code, you can call its isolated methods and access properties synchronously because you are already in the actor's safe context.

What does actor isolation protect in Swift concurrency?

A UI updates

B Only immutable data

C Shared mutable state from concurrent access

D Network requests

Actor isolation protects shared mutable state by allowing only one task to access the actor's data at a time.

How do you access an actor's property from outside the actor?

A Directly without any keyword

B Using synchronous calls

C Using try/catch

D Using async/await

You must use async/await to safely access an actor's isolated properties from outside.

Inside an actor, can you call its own isolated methods synchronously?

A Yes, because you are inside the actor

B No, always async

C Only if marked with @MainActor

D Only if the method is static

Inside the actor, synchronous calls to its own isolated methods are allowed because the code runs in the actor's safe context.

What error occurs if you access an actor's isolated property directly from outside without async/await?

A Runtime crash

B Compile-time error

C No error, it works fine

D Warning only

Swift produces a compile-time error to enforce actor isolation rules.

Which keyword is essential to mark a type as an actor in Swift?

A actor

B struct

C class

D enum

The 'actor' keyword defines a type with actor isolation in Swift.

Explain actor isolation and why it is important in Swift concurrency.

Think about how actors keep data safe when many tasks run at once.

Describe how you would safely access an actor's property from outside the actor.

Remember the rules Swift enforces to keep concurrency safe.

Practice

1. What is the main purpose of actor isolation in Swift concurrency?

easy

A. To disable concurrency features in Swift

B. To ensure only one task accesses actor data at a time

C. To make actor methods run faster without waiting

D. To allow multiple tasks to modify actor data simultaneously

Solution

1. Step 1: Understand actor isolation concept

   Actor isolation means only one task can access the actor's data at a time to avoid conflicts.

2. Step 2: Compare options with this concept

   Only To ensure only one task accesses actor data at a time correctly describes this purpose; others contradict the idea of isolation.

3. Final Answer:

   To ensure only one task accesses actor data at a time -> Option B

4. Quick Check:

   Actor isolation = single task access [OK]

Hint: Actor isolation means single task access only [OK]

Common Mistakes:

• Thinking actors allow simultaneous data changes
• Confusing isolation with performance boost
• Believing actor isolation disables concurrency

2. Which of the following is the correct way to call an actor's method from outside the actor in Swift?

easy

A. await actorInstance.method()

B. actorInstance.method()

C. async actorInstance.method()

D. actorInstance.method.await()

Solution

1. Step 1: Recall syntax for calling actor methods

   Calling an actor's method from outside requires using await to handle asynchronous access.

2. Step 2: Match options with correct syntax

   Only await actorInstance.method() uses await correctly before the method call.

3. Final Answer:

   await actorInstance.method() -> Option A

4. Quick Check:

   Use await before actor method call [OK]

Hint: Always use await before calling actor methods externally [OK]

Common Mistakes:

• Omitting await causing compile errors
• Using async keyword incorrectly
• Placing await after method call

3. Consider this Swift code snippet:

actor Counter {
    var value = 0
    func increment() {
        value += 1
    }
}

let counter = Counter()
Task {
    await counter.increment()
    print(await counter.value)
}

What will be printed when this code runs?

medium

A. 1

B. 0

C. Compilation error

D. Runtime crash

Solution

1. Step 1: Understand actor method and property access

   The method increment() increases value by 1. Accessing value outside requires await.

2. Step 2: Trace code execution

   The task calls await counter.increment() which adds 1, then prints await counter.value, so output is 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Increment then print value = 1 [OK]

Hint: Increment then await value to print updated number [OK]

Common Mistakes:

• Forgetting await on property access
• Assuming value remains 0 without increment
• Expecting compile or runtime errors

4. Identify the error in this Swift actor usage:

actor BankAccount {
    var balance = 1000
    func withdraw(amount: Int) {
        balance -= amount
    }
}

let account = BankAccount()
account.withdraw(amount: 100)
print(account.balance)

medium

A. Cannot print actor properties

B. balance should be a constant

C. withdraw method must be static

D. Missing await when calling actor method

Solution

1. Step 1: Check actor method call rules

   Calling an actor's method from outside must use await because it is asynchronous.

2. Step 2: Identify missing await

   The code calls account.withdraw(amount: 100) without await, causing a compile error.

3. Final Answer:

   Missing await when calling actor method -> Option D

4. Quick Check:

   Actor method calls need await [OK]

Hint: Always await actor method calls outside actor [OK]

Common Mistakes:

• Calling actor methods without await
• Thinking actor properties can't be printed
• Believing methods must be static

5. You want to safely update a shared counter from multiple tasks using an actor. Which approach correctly ensures safe concurrent increments?

hard

A. Use a global variable and increment without synchronization

B. Use a struct with a mutating method called from multiple tasks

C. Define an actor with a method to increment the counter and call it with await

D. Use a class with a property and increment it directly from tasks

Solution

1. Step 1: Understand concurrency safety requirements

   Shared data must be accessed safely to avoid race conditions; actors provide this by isolating data.

2. Step 2: Evaluate each option for safety

   Define an actor with a method to increment the counter and call it with await uses an actor with an increment method called with await, ensuring safe access. Others lack synchronization.

3. Final Answer:

   Define an actor with a method to increment the counter and call it with await -> Option C

4. Quick Check:

   Actor method with await ensures safe concurrent updates [OK]

Hint: Use actor methods with await for safe shared data updates [OK]

Common Mistakes:

• Ignoring synchronization with global variables
• Using structs or classes without concurrency control
• Assuming direct property access is safe