swift-concurrency-expert

To fix Swift concurrency data races, triage actor isolation and Sendable safety violations, apply minimal isolation boundaries, and leverage main-actor defaults to resolve diagnostics while preserving existing runtime behavior.

Migrating completion handlers to async/await involves replacing callback signatures with async functions and updating call sites to use await, resolving any resulting data-race diagnostics with minimal behavioral changes to ensure thread safety.

Sendable safety works by verifying that types crossing actor boundaries are thread-safe, requiring you to annotate or isolate non-conforming types to prevent data races during async/await migrations in Swift 6.2+ projects.

Yes, you can apply main-actor annotations to UI-heavy apps by leveraging main-actor defaults and using minimal actor isolation, which secures data access against races without introducing significant behavioral changes to the UI thread.

Data-race diagnostics appear after async/await migration because shared mutable state crosses actor boundaries unsafely, requiring you to triage Sendable conformance and apply proper actor isolation to remediate the concurrency issues.