swift-concurrency

Swift 6 migration requires resolving stricter concurrency checking by analyzing async/await and actor isolation boundaries to ensure thread-safe code. This Skill guides you through choosing the right concurrency primitives and resolving compiler warnings with minimal disruption.

Sendable warnings occur when types cross actor isolation boundaries unsafely in async/await code. This Skill analyzes your concurrency design and generates guidance to resolve Sendable conformance, fix isolation errors, and eliminate data race risks.

Handling actor isolation in SwiftUI requires applying @MainActor and custom isolation boundaries to prevent data races. This Skill analyzes your app's concurrency code and recommends safe async design patterns for UI updates and state management.

Fixing flaky concurrent tests and retain cycles involves identifying unsafe task-based concurrency and actor isolation mistakes. This Skill troubleshoots threading misconceptions and verifies thread-safe behavior for modernized iOS networking layers.

Using async let and task groups for Core Data access requires strict actor isolation and Sendable compliance to avoid data races. This Skill analyzes your data access patterns and generates safe concurrency boundaries for your workflows.

Actors are needed when you require custom isolation boundaries to protect mutable state, whereas async/await simply manages asynchronous execution. This Skill analyzes your code to determine the correct primitive for safe concurrent design.