swift-concurrency

To fix Swift data race errors, you must correctly apply actor isolation and Sendable conformance to your types. This Skill guides you through resolving strict concurrency diagnostics by ensuring your async code safely transfers data across isolation boundaries.

Approachable concurrency in Swift 6.2 introduces default MainActor isolation, @concurrent functions, and nonisolated(nonsending) to simplify migration. This Skill helps you adopt these features to write data-race-safe code while reducing strict concurrency compiler warnings.

Migrating to full Swift 6 strict concurrency involves replacing @preconcurrency wrappers with proper Sendable conformance and actor isolation. This Skill facilitates the transition by resolving strict concurrency diagnostics and applying the latest Swift 6.2 approachable concurrency features.

Yes, you can design actor-based architectures and leverage structured concurrency using TaskGroups to manage background work. This Skill aids in architecting your async code to safely offload tasks while maintaining data-race safety across actors.

Sendable conformance errors occur when types cross actor isolation boundaries unsafely, risking data races. This Skill resolves these errors by guiding you through correct Sendable adoption and actor isolation adjustments for your Swift concurrent code.