|
You are here |
massicotte.org | ||
| | | | |
swiftwithmajid.com
|
|
| | | | | Apple released Swift 5.5 almost three years ago. The main addition to the release was the Swift Concurrency feature. It introduced async and await keywords, allowing us to build concurrent apps in a new way. This week, we will learn how Swift determines where to run your function in a concurrent environment. | |
| | | | |
www.massicotte.org
|
|
| | | | | 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 without region-based isolation. | |
| | | | |
telemetrydeck.com
|
|
| | | | | What we've learned while migrating our code to the new world of data-race safety in Swift 6 mode. | |
| | | | |
limpet.net
|
|
| | | [AI summary] This article explains Rust's memory safety guarantees by reframing the compiler's borrowing and lifetime checks as a system of unique versus shared access to data. | ||