How to “ObjectContext” with Swift 6 concurrency

[vns]

@sliemeobn

I could also make the context thread-safe with traditional means, but why should it have to be? I think it is a feature to be forced into "one task owns this, one task works on this, no parallel funny-business"-mode. If we had async(inline) or @inheritIsolation it would all semantically click for me, as in "my async functions are not to be sent anywhere, but within them I will call async functions which will".

To summarize, I am still left feeling there is a missing feature set in swift's concurrency story when it comes to tying together non-sendable types into some dynamic isolation without resorting to (the very server-foreign) @MainActor.

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.