Swift Concurrency

Fast Path

Before proposing a fix:

1. Analyze Package.swift or .pbxproj to determine Swift language mode, strict concurrency level, default isolation, and upcoming features. Do this always, not only for migration work.
2. Capture the exact diagnostic and offending symbol.
3. Determine the isolation boundary: @MainActor, custom actor, actor instance isolation, or nonisolated.
4. Confirm whether the code is UI-bound or intended to run off the main actor.
5. Check if @Observable is in play - it changes how isolation inference works on the type.

Project settings that change concurrency behavior:

If any of these are unknown, ask the developer to confirm them before giving migration-sensitive guidance. Do not guess.

Guardrails:

• Do not recommend @MainActor as a blanket fix. Justify why the code is truly UI-bound.
• Prefer structured concurrency over unstructured tasks. Use Task.detached only with a clear reason.
• If recommending @preconcurrency, @unchecked Sendable, or nonisolated(unsafe), require a documented safety invariant and a follow-up removal plan.
• Optimize for the smallest safe change. Do not refactor unrelated architecture during migration.
• When @Observable is involved, understand that it does NOT automatically imply @MainActor isolation - the developer must explicitly opt in. Do not conflate the two.

Quick Fix Mode

Use Quick Fix Mode when all of these are true:

• The issue is localized to one file or one type.
• The isolation boundary is clear.
• The fix can be explained in 1-2 behavior-preserving steps.

Skip Quick Fix Mode when any of these are true:

• Build settings or default isolation are unknown.
• The issue crosses module boundaries or changes public API behavior.
• The likely fix depends on unsafe escape hatches.

Common Diagnostics

When Quick Fixes Fail

1. Gather project settings if not already confirmed.
2. Re-evaluate which isolation boundaries the type crosses.
3. Route to the matching reference file for a deeper fix.
4. If the fix may change behavior, document the invariant and add verification steps.

Smallest Safe Fixes

Prefer changes that preserve behavior while satisfying data-race safety:

• UI-bound state: isolate the type or member to @MainActor.
• Shared mutable state: move it behind an actor, or use @MainActor only if the state is UI-owned.
• Background work: when work must hop off caller isolation, use an async API marked @concurrent; when work can safely inherit caller isolation, use nonisolated without @concurrent.
• Sendability issues: prefer immutable values and explicit boundaries over @unchecked Sendable.
• @Observable view models: isolate the entire class to @MainActor when it drives UI; use nonisolated for computed properties or methods that don't touch UI state.

@Observable + @MainActor Quick Guide

This is one of the most common pain points in modern SwiftUI apps. The @Observable macro does NOT infer @MainActor - you must explicitly add it when the class drives UI.

The Core Pattern

// ✅ Correct: @MainActor view model with @Observable
@MainActor @Observable
final class ContentViewModel {
    var items: [Item] = []
    var isLoading = false

    func loadItems() async {
        isLoading = true
        items = await APIClient.fetchItems()
        isLoading = false
    }
}

SwiftUI Integration (Observation framework)

Use @State (not @StateObject) and @Environment (not @EnvironmentObject) with @Observable:

// ✅ Correct Observation-era SwiftUI
struct ContentView: View {
    @State private var viewModel = ContentViewModel()

    var body: some View {
        List(viewModel.items) { item in
            Text(item.name)
        }
        .task { await viewModel.loadItems() }
    }
}

// ✅ Passing via environment
@main
struct MyApp: App {
    @State private var library = Library()

    var body: some Scene {
        WindowGroup {
            LibraryView()
                .environment(library)
        }
    }
}

struct LibraryView: View {
    @Environment(Library.self) private var library

    var body: some View {
        List(library.books) { book in
            BookView(book: book)
        }
    }
}

Bindings with @Bindable

For two-way bindings to @Observable objects, use @Bindable:

struct EditView: View {
    @Bindable var viewModel: ContentViewModel

    var body: some View {
        TextField("Name", text: $viewModel.name)
    }
}

Common Mistakes

// ❌ Missing @MainActor - mutations from async contexts may happen off main thread
@Observable
final class ViewModel {
    var items: [Item] = []  // SwiftUI reads this - must be main-actor-isolated
}

// ❌ Using old ObservableObject patterns with @Observable
@Observable
final class ViewModel: ObservableObject {  // Don't conform to both
    @Published var items: [Item] = []      // @Published is for ObservableObject
}

// ❌ Using @StateObject with @Observable
struct MyView: View {
    @StateObject var vm = ViewModel()  // Use @State instead
}

For the full guide, see references/observable.md.

Concurrency Tool Selection

Common Scenarios

Network request with UI update

Task { @concurrent in
    let data = try await fetchData()
    await MainActor.run { self.updateUI(with: data) }
}

Processing array items in parallel

await withTaskGroup(of: ProcessedItem.self) { group in
    for item in items {
        group.addTask { await process(item) }
    }
    for await result in group {
        results.append(result)
    }
}

Swift 6 Migration Quick Guide

Key changes in Swift 6:

• Strict concurrency checking enabled by default
• Complete data-race safety at compile time
• Sendable requirements enforced on boundaries
• Isolation checking for all async boundaries

Migration Validation Loop

Apply this cycle for each migration change:

1. Build - Run swift build or Xcode build to surface new diagnostics
2. Fix - Address one category of error at a time (e.g., all Sendable issues first)
3. Rebuild - Confirm the fix compiles cleanly before moving on
4. Test - Run the test suite to catch regressions (swift test or Cmd+U)
5. Only proceed to the next file/module when all diagnostics are resolved

If a fix introduces new warnings, resolve them before continuing. Never batch multiple unrelated fixes - keep commits small and reviewable.

For detailed migration steps, see references/migration.md.

Reference Router

Open the smallest reference that matches the question:

• Foundations
• references/async-await-basics.md - async/await syntax, execution order, async let, URLSession patterns
• references/tasks.md - Task lifecycle, cancellation, priorities, task groups, structured vs unstructured
• references/actors.md - Actor isolation, @MainActor, global actors, reentrancy, custom executors, Mutex
• references/sendable.md - Sendable conformance, value/reference types, @unchecked, region isolation
• references/threading.md - Execution model, suspension points, Swift 6.2 isolation behavior
• Observation
• references/observable.md - @Observable + @MainActor patterns, SwiftUI integration, async access, migration from ObservableObject
• Streams
• references/async-sequences.md - AsyncSequence, AsyncStream, when to use vs regular async methods
• references/async-algorithms.md - Debounce, throttle, merge, combineLatest, channels, timers
• Applied topics
• references/testing.md - Swift Testing first, XCTest fallback, leak checks
• references/performance.md - Profiling with Instruments, reducing suspension points, execution strategies
• references/memory-management.md - Retain cycles in tasks, memory safety patterns
• references/core-data.md - NSManagedObject sendability, custom executors, isolation conflicts
• Migration and tooling
• references/migration.md - Swift 6 migration strategy, closure-to-async conversion, @preconcurrency, FRP migration
• references/linting.md - Concurrency-focused lint rules and SwiftLint async_without_await
• Glossary
• references/glossary.md - Quick definitions of core concurrency terms

Verification Checklist

When changing concurrency code:

1. Re-check build settings before interpreting diagnostics.
2. Build and clear one category of errors before moving on. Do not batch unrelated fixes into the same change.
3. Run tests, especially actor-, lifetime-, and cancellation-sensitive tests.
4. Use Instruments for performance claims instead of guessing.
5. Verify deallocation and cancellation behavior for long-lived tasks.
6. Check Task.isCancelled in long-running operations.
7. Never use semaphores or ad hoc locking in async contexts when actor isolation or Mutex would express ownership more safely.
8. When using @Observable, verify that UI-driving properties are accessed on @MainActor.