Nick LockwoodFeb 2

Swift concurrency nOOb question: if you're using Approachable Concurrency and you get warnings about using Sendable structs in non-main-actor contexts, is the recommended workaround to mark them as nonisolated?

Also, it seems odd to me that marking a struct as Sendable doesn't already exempt it from default MainActor isolation. Is there a good reason why you'd want to limit Sendable types to MainActor?

Show threadAndrew EadesFeb 2
@nicklockwood Some people are saying to switch off the default MainActor isolation. @mattiem I think has some thoughts on this.
Show threadRhys MorganFeb 2
@matadan @nicklockwood @mattiem 100% this. It causes far, far more problems than it solves, IMO. The fact there’s a huge language dialect in the same version, with differences that affects all code you import (including libraries, not designed with MainActor-default-isolation) is a bit baffling to me. I’d be far more in favour of it as an idea if it didn’t affect libraries you import…
Show threadMatt MassicotteFeb 2
@rhysmorgan @matadan @nicklockwood what do you mean about it affecting libraries you import?
Show threadRhys MorganFeb 2
@mattiem @matadan @nicklockwood As in, when your Xcode project is MainActor-isolated, the modules you import are affected by this MainActor-isolation too (at least as far as I’m aware?). I know PointFree and GRDB have both been affected by this quite significantly. Loads of people asking questions on the PointFree Slack where the solution is usually “switch to nonisolated default isolation”
Show threadRhys Morgan
@mattiem @matadan @nicklockwood Sorry, yeah, I should have clarified – the issue is the MainActor isolation, not Approachable Concurrency!
Feb 2 at 11:10amIvory for iOS