Nonisolated methods in Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a nonisolated method in an actor.

Swift

actor Counter {
    nonisolated func [1]() -> String {
        return "Hello from nonisolated method"
    }
}

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

Agreet

Bincrement

Ccount

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method name that implies state change like 'increment' or 'update' in a nonisolated method.

The method greet is declared as nonisolated to allow calling it without actor isolation.

2fill in blank

medium

Complete the code to mark the method as nonisolated in the actor.

Swift

actor Logger {
    [1] func log(message: String) {
        print(message)
    }
}

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

Anonisolated

Basync

Cisolated

Dstatic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'static' or 'async' instead of 'nonisolated'.

The nonisolated keyword allows the log method to be called without actor isolation.

3fill in blank

hard

Fix the error by adding the correct keyword to the method to make it nonisolated.

Swift

actor DataStore {
    func fetch() -> String {
        return "Data"
    }

    [1] func info() -> String {
        return "Info"
    }
}

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

Aisolated

Basync

Cnonisolated

Dstatic

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to mark the method as nonisolated causes isolation errors.

Adding nonisolated to info allows it to be called without actor isolation.

4fill in blank

hard

Fill both blanks to create a nonisolated static method inside an actor.

Swift

actor Service {
    [1] [2] func status() -> String {
        return "Running"
    }
}

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

Anonisolated

Bisolated

Cstatic

Dasync

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'isolated' and 'nonisolated' or forgetting 'static'.

The method is both nonisolated and static, so it can be called without actor isolation and without an instance.

5fill in blank

hard

Fill the blank to define a nonisolated async method inside an actor.

Swift

actor Network {
    [1] func fetchData() async -> String {
        return "Data fetched"
    }
}

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

Aisolated

Bnonisolated

Casync

Dstatic

Attempts:

3 left

💡 Hint

Common Mistakes

Putting async before func (invalid syntax; async belongs in the signature after ()).

Omitting nonisolated or using isolated.

The method is marked nonisolated before func and async after the parameters in the signature.

Practice

1. What is the main purpose of marking a method as nonisolated in a Swift actor?

easy

A. To allow the method to run outside the actor's isolation without needing await

B. To make the method private to the actor

C. To force the method to always run asynchronously

D. To prevent the method from accessing any properties

Solution

1. Step 1: Understand actor isolation

   Actors protect their data by isolating it, so methods usually run inside this isolation.

2. Step 2: Role of nonisolated

   Marking a method nonisolated means it runs outside this isolation and can be called without await.

3. Final Answer:

   To allow the method to run outside the actor's isolation without needing await -> Option A

4. Quick Check:

   Nonisolated method = runs outside isolation without await [OK]

Hint: Nonisolated means no await needed to call method [OK]

Common Mistakes:

• Thinking nonisolated methods are private
• Assuming nonisolated methods must be async
• Believing nonisolated methods cannot access any properties

2. Which of the following is the correct way to declare a nonisolated method inside a Swift actor?

easy

A. func nonisolated greet() { print("Hello") }

B. nonisolated func greet() { print("Hello") }

C. func greet() nonisolated { print("Hello") }

D. func greet() async nonisolated { print("Hello") }

Solution

1. Step 1: Recall correct syntax for nonisolated

   The nonisolated keyword comes before func in the method declaration.

2. Step 2: Check each option

   nonisolated func greet() { print("Hello") } correctly places nonisolated before func. Others place it incorrectly or add unnecessary keywords.

3. Final Answer:

   nonisolated func greet() { print("Hello") } -> Option B

4. Quick Check:

   Keyword nonisolated before func = correct syntax [OK]

Hint: Put nonisolated before func keyword [OK]

Common Mistakes:

• Placing nonisolated after func
• Adding async unnecessarily
• Using nonisolated as a function modifier

3. What will be the output of the following Swift code?

actor Counter {
    var count = 0
    nonisolated func printHello() {
        print("Hello")
    }
    func increment() {
        count += 1
    }
}

let counter = Counter()
counter.printHello()
// counter.increment() // requires await

medium

A. Compile error because printHello is nonisolated

B. Hello\n1

C. Hello

D. Runtime error because increment is not awaited

Solution

1. Step 1: Understand nonisolated method call

   The method printHello() is marked nonisolated, so it can be called directly without await.

2. Step 2: Analyze output

   Calling counter.printHello() prints "Hello". The increment method is commented out, so no other output.

3. Final Answer:

   Hello -> Option C

4. Quick Check:

   Nonisolated method prints Hello directly [OK]

Hint: Nonisolated methods run without await and print output [OK]

Common Mistakes:

• Expecting increment output without await
• Thinking nonisolated causes compile error
• Confusing runtime error with compile error

4. Consider this Swift actor code snippet:

actor Logger {
    var logs = [String]()
    nonisolated func printLog(_ message: String) {
        print(message)
    }
    func addLog(_ message: String) {
        logs.append(message)
    }
}

let logger = Logger()
logger.printLog("Start")
logger.addLog("Start")

What is the main issue with this code?

medium

A. addLog method must be marked nonisolated

B. Nonisolated method printLog cannot access actor's logs array

C. Nonisolated method printLog causes data race on logs

D. Cannot call addLog without await, causing a compile error

Solution

1. Step 1: Check method calls

   The addLog method is isolated and must be called with await outside the actor.

2. Step 2: Identify error

   Calling logger.addLog("Start") without await causes a compile error.

3. Final Answer:

   Cannot call addLog without await, causing a compile error -> Option D

4. Quick Check:

   Isolated method call requires await [OK]

Hint: Isolated methods need await; nonisolated do not [OK]

Common Mistakes:

• Thinking nonisolated can access isolated properties
• Assuming addLog can be called without await
• Marking all methods nonisolated incorrectly

5. You want to add a nonisolated method to a Swift actor that returns a constant string without accessing any actor-isolated data. Which of the following implementations is correct and safe?

hard

A. nonisolated func status() -> String { return "Ready" }

B. nonisolated func status() -> String { return logs.first ?? "Ready" }

C. func status() async -> String { return "Ready" }

D. func status() -> String { return "Ready" }

Solution

1. Step 1: Identify safe nonisolated method

   A nonisolated method must not access actor-isolated data like logs.

2. Step 2: Evaluate options

   nonisolated func status() -> String { return "Ready" } returns a constant string without accessing isolated data, so it's safe and correct.

3. Final Answer:

   nonisolated func status() -> String { return "Ready" } -> Option A

4. Quick Check:

   Nonisolated method returns constant, no isolated data access [OK]

Hint: Nonisolated methods must avoid actor-isolated data [OK]

Common Mistakes:

• Accessing isolated properties inside nonisolated methods
• Making nonisolated methods async unnecessarily
• Ignoring actor isolation rules