Swift 6 rolls out a default main‑actor execution model and tightens protocol conformance rules. By marking a protocol requirement as nonisolated, developers signal that the method or property can be accessed synchronously from any actor. This shift forces a rethink of how actors expose data.

When an actor implements a nonisolated property, callers no longer need to await. However, if the actor itself runs on the main thread, the property becomes a potential race point when accessed from background actors. The compiler warns with “crosses into main actor‑isolated code” to flag this danger.

Developers can resolve the warning in two ways. First, declare the entire class nonisolated, which removes actor protection but may expose other state. Second, annotate the conformance with @MainActor so the property stays on the main thread, eliminating the need for nonisolated. The same logic applies to Encodable conformance, where encoding must run off‑main to avoid blocking.

These changes underscore Swift’s push toward safer concurrency. As developers refactor legacy code, they’ll need to audit protocol requirements and actor boundaries. Future Swift releases may relax some constraints, but for now, understanding nonisolated and @MainActor annotations is essential for building responsive, race‑free apps.