swift-concurrency-expert

预期结果:

• This error occurs because PhotoProcessor is being passed from a @MainActor context to a nonisolated method.
• Recommended fixes (choose based on your use case):
• 1. Make the calling type @MainActor isolated (if UI-bound)
• 2. Make PhotoProcessor nonisolated with @concurrent for background work
• 3. Use isolated protocol conformances if Exportable is involved
• 4. Apply main-actor-by-default mode in project settings for simpler annotations

预期结果:

• This error appears because global static variables can be accessed from multiple threads.
• Common solutions:
• - Annotate the static property with @MainActor
• - Wrap the type in an actor for internal isolation
• - Enable 'Approachable Concurrency' mode to infer @MainActor by default
• - Use @unchecked Sendable only if you can prove thread safety

预期结果:

• Structs with closure properties require careful handling for Sendable conformance.
• Options:
• 1. Make the closure @Sendable and ensure it captures no mutable state
• 2. Use @unchecked Sendable if the closure is verified thread-safe
• 3. Redesign to use value types instead of reference types
• 4. Move closure-heavy logic into a dedicated actor