Also, we're finally fixing the thing where we don't have a good cross platform mutex API, and even the platform specific one (OSAllocatedUnfairLock) requires a separate malloc for no good reason: https://forums.swift.org/t/pitch-synchronous-mutual-exclusion-lock/69889
- he/him or they/them
- dscoder.com/
“Listen: David Smith has come unstuck in time.” — Kurt Vonnegut, probably
Cohost bonus feature: 80% less professional
posts from @Catfish-Man tagged #swift concurrency
also:
It's interesting how wildly differently various subsets of the programming community react to design decisions.
"Pending work on Swift actors is priority-ordered rather than FIFO, and each time you await the post-await code is just regular pending work so may not run next"
App community: "why would they do it this way?? This is terrible????"
Some friends with a lot of distributed systems experience: "well yeah, obviously, how else would you do it?"
(Tragically, neither group is wrong, there's genuinely conflicting requirements here unless someone comes up with something clever and novel)
This is one I’m gonna have to set aside some time to read very carefully, since it’s potentially important to my work. https://forums.swift.org/t/pitch-custom-actor-executors/63135
I wrote a little explainer on what threads are, how Swift Concurrency uses the underlying operating system’s threads, and why that design can have benefits: https://www.reddit.com/r/swift/comments/wm3get/whats_the_difference_between_a_thread_and_a_task/ijx3uay/