swift-concurrency-6-2

To migrate your Swift project and avoid data races, adopt Approachable Concurrency by keeping async work on the caller's actor by default, enabling isolated conformances, and following progressive migration steps to Swift 6.2.

MainActor default isolation in Swift 6.2 makes app targets single-threaded by default to reduce data races, significantly reducing boilerplate while ensuring safe protocol conformances without explicit annotations.

You should use the @concurrent attribute in Swift when annotating performance-critical methods for CPU-intensive tasks that require explicit concurrency outside the default actor-isolated execution.

Yes, Swift 6.2 supports isolated conformances, enabling MainActor-safe protocol conformances that keep async operations on the caller's actor by default to prevent data races during migration.

The best way to enable MainActor default inference is to activate it in your Swift project settings and annotate only CPU-heavy methods with @concurrent, adopting Swift 6.2 concurrency progressively through structured migration steps.

Your Swift async code has data race safety issues because new concurrency features like MainActor default isolation require proper guidance; applying isolated conformances and keeping async work on the caller's actor resolves these pitfalls.