The whole nonisolated / @.concurrent changes in Swift 6.2 still don’t really sit right with me.
It feels MORE confusing to me that an async call will be on the same actor as its caller… That the behaviour has totally flipped, determined by a compiler flag… it’s just confusing.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/rhysmorgan/statuses/115904756256949329 on your instance and quote it. (Note that quoting is not supported in Mastodon.)