Current experiment that I think I hate, but addresses at least my common situation, which is unit tests writing something and then trying to read it.

public nonisolated func synchronize() async {
await Task{}.value
}

I worry this method implies more than it delivers. It doesn't promise that *all* enqueued Tasks have completed, just the ones created by the current context. Which is meaningful, but might still bite folks if they don't think about it carefully.

@cocoaphony I'm sure you're aware of this, so this is really for my understanding - SE-0472's Task.immediate would fix this, right?

https://github.com/swiftlang/swift-evolution/blob/main/proposals/0472-task-start-synchronously-on-caller-context.md