swift-concurrency

Fix Swift concurrency data races by applying structured triage workflows to diagnose actor isolation boundaries and validate Sendable compliance. This provides concrete checks to safely resolve data races and complex isolation conflicts.

Migrate to default MainActor isolation in Swift 6 by following structured guidance to reduce boilerplate and define nonisolated behavior. This safely transitions UI modules to modern Swift concurrency patterns while maintaining isolation boundaries.

Offload CPU-bound work in Swift structured concurrency by delegating tasks to @concurrent functions and utilizing Task.immediate. This pattern safely moves heavy processing off the MainActor to prevent UI freezing without violating Sendable safety.

Yes, this Swift concurrency migration approach explicitly supports isolated conformances and transactional observations. It defines requirements for implementing these patterns safely, reducing boilerplate while ensuring strict actor isolation and Sendable compliance.

Use actor isolation when managing shared mutable state across concurrent contexts to prevent data races, and apply nonisolated behavior for stateless operations. This distinction ensures safe default isolation boundaries and proper structured concurrency patterns.