swift-concurrency-expert

Fix Swift 6.2 concurrency errors by diagnosing actor isolation violations and adding appropriate Sendable conformance, @MainActor annotations, or async/await migrations to ensure minimal behavior changes while resolving data race diagnostics.

Actor isolation mismatches occur when code crosses isolation boundaries without proper synchronization. Resolve them by applying isolated protocol conformances, marking functions nonisolated, or migrating callback-style code to async/await under strict concurrency settings.

Make Swift types Sendable by adding explicit Sendable conformance, ensuring properties are immutable or thread-safe, using actors for mutable state, and applying @MainActor where UI or global state requires specific isolation.

Migrate callback-style Swift code to async/await by replacing completion handlers with async functions, adjusting execution with @concurrent where needed, and ensuring all captured values conform to Sendable for safe concurrent execution.

Yes, you can fix Swift concurrency warnings without changing app behavior by applying minimal, behavior-preserving edits such as adding correct Sendable conformance, using @MainActor for UI state, and resolving actor-isolation mismatches with isolated protocol conformances.

You need @MainActor annotations in Swift 6.2 when your code touches UI or global state that must execute on the main thread, ensuring safe access under strict concurrency settings without introducing data races.