Jan EkholmOne day I need to learn wtf this @ sendable stuff is that Xcode whines about nowadays. It seems to be something that should be simple that has gone through a concurrent swiftification and instantly become hard to understand and impossible to implement correctly. Everything about concurrency in Swift feels unnecessarily complicated and cursed. Or maybe I’m just too dumb for for this? Very plausible.
Mattes@chakie Honestly I feel the same and I wonder if developers working in other languages went through something similar. I can't remember, really. Or maybe it's just because I experience the evolution of Swift firsthand, whereas I didn't with other languages. 🤷🏼♂️
@mattesmohr I guess that if you know how to use the Swift version of concurrency correctly you will end up with applications that are safe from a concurrency point of view. But everything feels like a convoluted hack and it’s incredibly hard to do even remotely correctly. Just a few async calls easily poison the entire code base to be async. It feels like all this could have been a thread class and a mutex.