Complete Concurrency Checking

[PSchmiedmayer]

Problem

With Swift 6 approaching in a few months and nightly builds already being available we should ensure that all our packages are working well with all Swift concurrency checks.

The goal would be to support Swift 6 right from the start. We should consider selectively making some of our packages Swift 6 exclusive in case we require features only available in the next major version but should ideally support Swift 5.10 while Swift 6 adoption is picking up.

Solution

Each Spezi Package should enable strict concurrency checking in a PR and ensure that we don't have any warnings remaining in the packages as we develop new features or fix bugs from now. All UI test apps in the projects need to enable these flags by default.

• [ ] https://github.com/StanfordSpezi/Spezi/issues/103
• [ ] https://github.com/StanfordSpezi/SpeziLLM/issues/54
• [ ] https://github.com/StanfordSpezi/SpeziChat/issues/15
• [ ] https://github.com/StanfordSpezi/SpeziAccessGuard/issues/21
• [ ] https://github.com/StanfordSpezi/SpeziBluetooth/issues/21
• [ ] https://github.com/StanfordSpezi/SpeziMedication/issues/13
• [ ] https://github.com/StanfordSpezi/SpeziHealthKit/issues/21
• [ ] https://github.com/StanfordSpezi/SpeziQuestionnaire/issues/24
• [ ] https://github.com/StanfordSpezi/SpeziFirebase/issues/30
• [ ] https://github.com/StanfordSpezi/SpeziScheduler/issues/40
• [ ] https://github.com/StanfordSpezi/SpeziFileFormats/issues/5
• [ ] https://github.com/StanfordSpezi/SpeziAccount/issues/55
• [ ] https://github.com/StanfordSpezi/SpeziStorage/issues/20
• [ ] https://github.com/StanfordSpezi/SpeziContact/issues/26
• [ ] https://github.com/StanfordSpezi/SpeziOnboarding/issues/47
• [x] https://github.com/StanfordSpezi/SpeziLicense/issues/3
• [ ] https://github.com/StanfordSpezi/SpeziFoundation/issues/8
• [ ] https://github.com/StanfordSpezi/SpeziViews/issues/35
• [ ] https://github.com/StanfordSpezi/SpeziFHIR/issues/19
• [ ] https://github.com/StanfordSpezi/SpeziSpeech/issues/6
• [ ] https://github.com/StanfordSpezi/SpeziMockWebService/issues/16

In a final step, the Spezi Template Application and Spezi Study Application should enable strict concurrency checking to demonstrate that we fully support it in using applications.

• [ ] https://github.com/StanfordSpezi/SpeziTemplateApplication/issues/76
• [ ] https://github.com/StanfordSpezi/SpeziStudyApplication/issues/10

Additional context

We should consider adding SWIFT_TREAT_WARNINGS_AS_ERRORS = YES to our general workflows to enforce that all warnings are flagged as errors during our CI setup.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct and Contributing Guidelines