2026-04-16 01:46 UTC
This blog post is a great example of how and why Swift Concurrency is an absolute mess.
Nonsensical default behavior. Opaque keywords and modifiers that require too much cognitive load.
A special case for *everything*.
You couldn’t design a more complicated and confusing system if you tried.
https://alejandromp.com/development/blog/a-small-swiftui-warning-and-a-long-journey-to-understand-it
Replies (2)
-
@danielinoa@mastodon.social 2026-04-16 02:42
@jsq Swift engineers need to release a definite guide for Swift Concurrency with meaningful code samples. The WWDC videos are cool but there are still too many gaps. Talking about nonsensical defaults, I wrote something about how something as simple as the HStack initializer manages to fumble a default: https://danielinoa.com/posts/swiftui-default-stack-spacing
-
@mattiem@mastodon.social 2026-04-16 11:35
@jsq I am deeply sympathetic to this position. Unfortunately the root cause here is just a compiler bug I'm pretty sure. Which, itself, is really awful because a ground truth of how the compiler actually functions is a huge component in building understanding or confusion. Which is what this post is actually about.