If you wish to make it possible for your code adopts Swift concurrency as appropriately as attainable in Swift 5.7, it is a good suggestion to allow the Strict Concurrency Checking (SWIFT_STRICT_CONCURRENCY) in your mission.
To do that, choose your mission’s goal and navigate to the Construct Settings tab. Be sure you choose All from the record of settings that’s proven (Fundamental is the default) and kind Strict Concurrency within the searchbar to search out the Strict Concurrency Checking construct setting.
The screenshot beneath exhibits all of the related elements so that you can see:
The default worth for this setting is Minimal which boils right down to the Compiler solely checking specific Sendable annotations amongst different issues. This setting is the least restrictive and enforces as little of Swift Concurrency’s constraints as attainable in the interim.
You may bump your checking to Focused which can implement Sendable and actor-isolation checks in your code, and it’ll explicitly very that Sendable constraints are met if you mark one among your varieties as Sendable. This mode is basically a little bit of a hybrid between the conduct that is supposed in Swift 6, and what’s allowed now. You should use this mode to have a little bit of checking in your code that makes use of Swift Concurrency with out an excessive amount of warnings and / or errors in your present codebase.
With Full you’re going to get the total suite of concurrency constraints, basically as they are going to work in Swift 6. Personally I might advocate enabling this setting for brand spanking new initiatives the place you need your entire code to be correctly checked instantly. In an present codebase this mode could be just a little too strict, however however it would flag numerous issues that might be necessary in Swift 6.
