Discussion
A persistent complaint about Swift's concurrency system is that it keeps changing. And yes, lots of new features have been added.
But aside from back-and-forth in one very specific area (and now settled with NonisolatedNonsendingByDefault), the programming model has really remained unchanged.
@mattiem And yet, it's still written as a CS thesis. The first paragraph of this feature "Prior to this feature, nonisolated async functions never run on an actor’s executor and instead switch to global generic executor. The motivation was to prevent unnecessary serialization and contention for the actor by switching off of the actor to run the nonisolated async function, but this does have a number of unfortunate consequences:" 🫨
@mattiem So I need to clear an afternoon, put DND and ask an LLM to translate this to human English with "actual" consequences and constraints. After I take stock of the versions of both Swift and Xcode of the project :D ... so yeah, let's call that another persistence complaint :D
I think I posted it in another thread, Wishlist for WWDC27: breaking Swift 7 where someone prunes everything so it fits in 20 keywords.
@iamkonstantin poorly written documentation is a problem, yes.
I hope that process helps you!
As I’m sure you know, you will not get your wish.
@mattiem Of course I know. It's just triggering to read statements trying to normalise the clearly suboptimal situation. I'm sure everyone involved is doing their best, but look, even the 'fix' - someone decided to call this NonisolatedNonsendingByDefault. So if you do swift package init is it on? Can you check? The first reason listed for it to exist is to solve "nonisolated" being difficult to understand and yet it's the first keyword of the flag name... I know language design is hard.
@iamkonstantin I would like you to consider the possibility that this conversation, as well as the suggestion writing about and explaining about a technical topic I do for a living will be done by an LLM, is also triggering.
@mattiem I was being sarcastic to mean that if you're outside the "compiler bubble", there are very few places you could turn to short of spending a lot of time experimenting and debugging with tools clearly not made for this.
@iamkonstantin oh, my apologies if that was my misinterpretation of a joke!
@mattiem I really wasn't joking :D. I don't consider LLMs a reliable source of information and so it didn't occur to me you may be reading it more literally 🙈
Install bonfire.cafe
Get the full app experience
