Sendable gets talked about a lot. And while it is a critical aspect of Swift concurrency, I think non-Sendable types are very interesting and just as important. They are often seen as a problem when facing concurrency issues. But, non-Sendable types can actually sometimes be a perfect solution.
Wrote this up in kind of hurry, but people seem to like it. Thought I’d throw it up over here.
Dictionary is a value type so it is stack-allocated. But that value is a pretty thin wrapper around a heap-allocated backing store. I’m not sure how useful it is to think about or even know that detail. I hate doing the cliché thing here, but can I ask why you are asking?
If anyone has any feedback on the content, I'd love to hear! You can also check out the sources and even get involved here: https://github.com/apple/swift-migration-guide
Concurrency in Swift 6: SE-0414
Earlier in this series, I said that there are three proposals that will have a profound effect on how Swift concurrency is used. This one definitely falls into that category. But, I don’t think the word “profound” even goes far enough. I’m not sure how the Swift 6 language mode would be possible wit...
Hey all! I've been writing up a series on the changes coming to Swift 6 related to concurrency. Thought I'd start sharing them here too.
This preview covers the specs and my initial impressions of Ubiquiti’s latest batch of Wi-Fi 7 UniFi access points: the U7 Pro Max, U7 Pro Wall, and U7 Outdoor.
I'm excited for this! I tried out Mlem, but it sounds like it isn't being worked on anymore. I'm bootstrapping, so finding communities is pretty important to me. Can't wait to see what you've been putting together.