How to “ObjectContext” with Swift 6 concurrency

I liked naming @isolated(any) / @isolated(caller) - if I understood correctly its purpose - from here. Totally agree that Swift missing that level of isolation control, even with @MainActor in Apple's ecosystem, if you do not want simply mark everything with it, you have not so much options.

From my understanding, there is not so much cases when you need to make something an actor, if as you described, one task owns-one task works with it, is the only way you are going to work with it. So making each time some type an actor seems wrong.

1 Like