swift-concurrency-6-2

Swift 6.2 migration triggers data race safety errors because implicit background offloading and ambiguous actor isolation cause accidental cross-thread access. You can resolve this by adopting single-threaded default behavior and isolated conformances for MainActor types.

To conform a MainActor-isolated type to a non-isolated protocol safely, use isolated conformances in Swift 6.2. This explicitly defines isolation boundaries so nonisolated contexts cannot incorrectly access those conformances and trigger data races.

Use @concurrent in Swift 6.2 when you need real parallelism for CPU-intensive work. Marking functions with @concurrent deliberately offloads execution to the background, requiring await at call sites to maintain correct async behavior and prevent data races.

Yes, Swift 6.2 keeps async work on the calling actor by default. This single-threaded default behavior prevents accidental cross-thread access and implicit background offloading, ensuring data race safety during migration without explicit annotations.

MainActor default inference mode allows MainActor inference for app targets and executable code paths in Swift 6.2. This approach reduces boilerplate by automatically applying MainActor isolation, reducing the need for explicit annotations while maintaining safe concurrency.