Actor isolation concept in Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare an actor named Counter.

Swift

actor [1] {
    var value = 0
}

Drag options to blanks, or click blank then click option'

ACounter

Bclass

Cstruct

Denum

Attempts:

3 left

💡 Hint

Common Mistakes

Using class, struct, or enum instead of actor.

The keyword actor declares an actor type named Counter.

2fill in blank

medium

Complete the code to define an isolated method increment() inside the actor.

Swift

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

Drag options to blanks, or click blank then click option'

Adecrement

Bincrement

Creset

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using method names that do not match the action, like decrement or reset.

The method increment() increases the value by 1 inside the actor.

3fill in blank

hard

Fix the error by completing the code to call the isolated method increment() from outside the actor.

Swift

let counter = Counter()
Task {
    await counter.[1]()
}

Drag options to blanks, or click blank then click option'

Areset

Bvalue

Cinit

Dincrement

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to access the property directly without await.

Using wrong method names.

Calling an isolated actor method from outside requires await and the method name increment().

4fill in blank

hard

Fill both blanks to define an isolated computed property and access it asynchronously.

Swift

actor Counter {
    var value = 0
    var [1]: Int {
        return value
    }
}

let counter = Counter()
Task {
    let currentValue = await counter.[2]
}

Drag options to blanks, or click blank then click option'

AcurrentValue

Bvalue

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the property and access.

Not using await when accessing the property.

The isolated computed property is named value and accessed asynchronously with await counter.value.

5fill in blank

hard

Fill all three blanks to define an actor with an isolated method, call it asynchronously, and print the result.

Swift

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

let counter = Counter()
Task {
    await counter.[2]()
    print(counter.[3])
}

Drag options to blanks, or click blank then click option'

Aincrement

Cvalue

DcurrentValue

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong method or property names.

Not using await when calling the method.

The method increment() increases the value, which is then printed by accessing value.

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