I might just define a my own

expect synchronized

for now and alias it to the JVM implementation for Android, for iOS just pass through in the knowledge that its coroutines are single threaded anyway.

i was told that's the way to go when i asked pretty mcih the same question a few months ago

I wrote Stately and can speak to this. If you know for sure that only one thread will access the

synchronized

block, it should be OK, but my immediate question would be why do you need it at all? Why is iOS OK doing everything on the main thread but JVM isn’t?