axiom-swift-concurrency

To fix Swift 6 data race errors, you must adopt strict concurrency patterns using actor isolation and Sendable types. This ensures safe data handling across threads by preventing concurrent access to mutable state.

Use Swift actors when you need to protect mutable state from concurrent access, and use async/await for managing asynchronous operations. Actors provide synchronization, while async/await structures the execution flow.

Making Swift types Sendable requires ensuring they are safe for concurrent access across threads. You achieve this by conforming to the Sendable protocol, often by using value types or actor isolation.

Sending 'self' risks causing data races because background network calls execute concurrently with the main UI thread. You must use actor isolation or Sendable conformances to safely pass data across these execution boundaries.

You can adopt Swift 6 concurrency progressively by migrating single-threaded execution models to concurrent ones incrementally. This strategy involves isolating specific components with actors and gradually conforming types to Sendable.