Why Nonisolated methods in Swift? - Purpose & Use Cases

The Big Idea

What if you could skip waiting for your code to switch threads for simple tasks?

The Scenario

Imagine you have a class that runs tasks on a background thread to keep your app smooth. Now, you want to call a simple method that just returns a value without changing anything. If you treat this method like all others and force it to run on the background thread, you waste time and make your code complicated.

The Problem

Calling every method on the background thread slows down your app and makes your code harder to read. You might also accidentally cause delays or crashes because you block the main thread or mix thread contexts. Managing which methods run where becomes a big headache.

The Solution

Nonisolated methods let you mark simple, safe methods to run anywhere without waiting for the actor's queue. This means you can quickly get values or do simple checks without the overhead of switching threads. Your code stays clean, fast, and easy to understand.

Before vs After

✗ Before

actor MyActor {
  func getValue() async -> Int {
    return 42
  }
}

let myActor = MyActor()
let value = await myActor.getValue()

✓ After

actor MyActor {
  nonisolated func getValue() -> Int {
    return 42
  }
}

let myActor = MyActor()
let value = myActor.getValue()

What It Enables

You can write safer, faster code by clearly separating methods that need isolation from those that don't, improving app performance and simplicity.

Real Life Example

In a chat app, you might have an actor managing messages. A nonisolated method can quickly return the current user's name without waiting for the actor's queue, making the UI more responsive.

Key Takeaways

Manual thread management for every method is slow and complex.

Nonisolated methods let simple, safe methods run anywhere instantly.

This improves code clarity, speed, and app responsiveness.