{"id":32851,"date":"2021-06-14T16:34:23","date_gmt":"2021-06-14T20:34:23","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32851"},"modified":"2021-06-14T16:34:23","modified_gmt":"2021-06-14T20:34:23","slug":"concurrency-in-swift-5-and-6-data-races","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/06\/14\/concurrency-in-swift-5-and-6-data-races\/","title":{"rendered":"Concurrency in Swift 5 and 6: Data Races"},"content":{"rendered":"

Douglas Gregor<\/a>:<\/p>\n

An explicit goal of the concurrency effort for Swift 6 is to make safe-by-default also extend to data races. The type system and language model work together, through features like actors, Sendable<\/code>, and global actors, to eliminate data races.<\/p>

However, there is a lot of Swift code out there that was developed without the Swift concurrency model. Some portion of that code is going to have to change to fit within the constraints of Swift’s concurrency model, but it’s not going to be rewritten in a month or even a year. We need to consider what it’s going to look like to migrate the Swift ecosystem to Swift 6, and expect that this process will take years.<\/p>

[…]<\/p>

To enable the incremental rollout of Swift 6’s safe-by-default for data races, we’ll allow the use of concurrency features in Swift 5 with a “relaxed” enforcement model that allows incremental adoption[…]<\/p><\/blockquote>\n\n

See also: Swift by Sundell<\/a>.<\/p>\n\n

Previously:<\/p>\n