swift-concurrency

Swift 6 migration involves enabling strict concurrency settings, addressing data races, and adopting actor isolation. This Skill provides actionable migration steps, best practices, and concrete patterns to safely transition your existing codebase to structured concurrency.

Actor isolation protects mutable state by serializing access, preventing data races in Swift Concurrency. This Skill provides concrete patterns for using actors and Sendable types to ensure safe, efficient concurrent code without reentrancy pitfalls.

Yes, async/await patterns apply to both apps and libraries, requiring strict Sendable conformance and actor isolation. This Skill provides a pattern library with concrete examples for tasks, actors, and Sendable types to ensure safe concurrency across different Swift project types.

Debugging Swift concurrency issues requires understanding structured concurrency and identifying unsafe data access patterns. This Skill guides you through best practices and concrete patterns to minimize reentrancy risks and resolve data races effectively.

Sendable types are needed when passing data across concurrent boundaries to compile under Swift 6 strict concurrency. This Skill provides concrete patterns and best practices for conforming types to Sendable, ensuring safe data access across actors and tasks.