swift-concurrency-6-2

Swift 6.2 keeps async functions on the calling actor by default, so most implicit offloading data races disappear once you enable approachable concurrency build settings. For remaining issues, annotate shared state with @MainActor or use isolated conformances instead of nonisolated workarounds.

@concurrent explicitly offloads a function to the background thread pool for CPU-intensive work like image processing. Mark the containing type nonisolated, add @concurrent and async to the function, and use await at call sites.

No. Swift 6.2 offers an opt-in MainActor default inference mode where types, properties, and conformances are implicitly @MainActor without manual annotations. This mode is recommended for apps, scripts, and other executable targets.

Yes, using isolated conformances such as extension StickerModel: @MainActor Exportable. The compiler ensures the conformance is only used on the main actor, rejecting it in nonisolated contexts at compile time.

Avoid applying @concurrent to every async function, since most code does not need background execution. Profile with Instruments first and offload only CPU-intensive hot paths like image processing, compression, or complex computation.