You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In September Apple will release Swift 6 which introduces compile-time safety against data-races in concurrent code. As we have web callbacks in the repo, it's very likely we will have some failures that need to be fixed in Swift 6 mode.
In the related WWDC session this year Apple urged third-party framework developers to adopt Swift 6 language mode fast so our community can profit from the additional safety. So we should turn on "complete concurrency checking" for Swift 5 in Xcode 16 beta before September and fix any warnings and make a release with the fixes up-front.
This should make the lib ready for Swift 6 language mode, which when enabled should not cause any build errors any more. I'm not sure how things work with enabling Swift 6 language mode in packages that want to support older Xcode versions, I'd research that. But the "complete concurrency checking" should have the same effect as we would get warnings.
@winsmith Not sure which board this fits into best. It's not super urgent, probably August is a good time to tackle this.
The text was updated successfully, but these errors were encountered:
Jeehut
changed the title
Add support for data-race safety in Swift 6 language mode
Add support for data-race safety in Xcode 16
Jun 28, 2024
I can't think of a good board either, but I agree we should tacke this! I'm adding it to the "Bugs and Papercuts" board for now, just so it doesn't get lost.
In September Apple will release Swift 6 which introduces compile-time safety against data-races in concurrent code. As we have web callbacks in the repo, it's very likely we will have some failures that need to be fixed in Swift 6 mode.
In the related WWDC session this year Apple urged third-party framework developers to adopt Swift 6 language mode fast so our community can profit from the additional safety. So we should turn on "complete concurrency checking" for Swift 5 in Xcode 16 beta before September and fix any warnings and make a release with the fixes up-front.
This should make the lib ready for Swift 6 language mode, which when enabled should not cause any build errors any more. I'm not sure how things work with enabling Swift 6 language mode in packages that want to support older Xcode versions, I'd research that. But the "complete concurrency checking" should have the same effect as we would get warnings.
@winsmith Not sure which board this fits into best. It's not super urgent, probably August is a good time to tackle this.
The text was updated successfully, but these errors were encountered: