If you wish to make it possible for your code adopts Swift concurrency as appropriately as potential in Swift 5.7, it is a good suggestion to allow the Strict Concurrency Checking (SWIFT_STRICT_CONCURRENCY) in your venture.
To do that, choose your venture’s goal and navigate to the Construct Settings tab. Ensure you choose All from the checklist of settings that’s proven (Primary is the default) and kind Strict Concurrency within the searchbar to seek out the Strict Concurrency Checking construct setting.
The screenshot under reveals all of the related components so that you can see:
The default worth for this setting is Minimal which boils all the way 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 potential in the meanwhile.
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 whenever you mark one among your sorts as Sendable. This mode is basically a little bit of a hybrid between the habits that is meant in Swift 6, and what’s allowed now. You should utilize 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’ll get the total suite of concurrency constraints, primarily as they may work in Swift 6. Personally I’d advocate enabling this setting for brand new initiatives the place you need your whole code to be correctly checked instantly. In an current codebase this mode could be a bit of too strict, however alternatively it would flag a number of issues that shall be necessary in Swift 6.