/explore
|
You are here 
|
trycombine.com | ||
| | | | |
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
Swift 5.9 introduced a feature, via SE-0392, called custom actor executors. This was a low-level concurrency feature that made it possible to control the context an actor uses for execution. You don't need to understand the how or even the why here. All that's important is to know that without that change, some pre-existing systems could not easily integrate into Swift's concurrency model. |
|
| | | | | ||
| | | | |
www.avanderlee.com
Unit testing async/await logic can be done by marking your unit test as asynchronous and using a new XCTest method. |
|
| | | | | ||
| | | | |
www.onswiftwings.com
Using property wrappers to define atomic properties in Swift |
|
| | | |||
