swift-concurrency

To resolve Swift data race errors, correctly apply actor isolation or add Sendable conformance to the types being passed across concurrency boundaries. This Skill diagnoses strict concurrency diagnostics and provides the exact steps to resolve them.

Adopting Swift 6.2 approachable concurrency involves using features like @concurrent, nonisolated(nonsending), and Task.immediate to write data-race-safe async code. This Skill guides you through applying these specific modifiers to migrate toward full strict concurrency.

Designing an actor-based architecture in Swift involves using actors to isolate state and structured concurrency with TaskGroup to manage background work offloading. This Skill assists in structuring these components to ensure robust and efficient concurrent applications.

Migrating from @preconcurrency to full Swift 6 strict concurrency requires resolving Sendable conformance issues and default MainActor isolation warnings. This Skill facilitates the transition by addressing strict concurrency diagnostics and adopting approachable concurrency patterns.

Sendable conformance compiler errors occur because types crossing actor boundaries are not marked as safe for concurrent use. This Skill resolves these Swift concurrency errors by guiding you through proper Sendable adoption and actor isolation.