> I just looked it up. It is Swift's version of async/await. Since you “just looked it up”, maybe don’t make blind assertions about something you clearly don’t

> I just looked it up. It is Swift's version of async/await. Since you “just looked it up”, maybe don’t make blind assertions about something you clearly don’t know very much about? It’s a lot more than async/await. It is a way to offer compile time guarantees about thread safety (through Sendable, which is part of SC), it’s an actor model (allowing shared mutable state to be isolated, leveraging async/await for coordination so that callers can pause if the actor is currently servicing another message) and a bunch more stuff. I explained all this in my post you replied to, maybe read the whole thing before making wrong claims about stuff you spent 1 minute looking up?