Added support for Swift 6 / Strict Concurrency #437
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Zandor300
requested changes
Mar 20, 2025
Zandor300
force-pushed
the
somerandomiosdev/strict-concurrency
branch
from
51ef2f2 to
bbfd0f8
Compare
|
@SomeRandomiOSDev Why all the |
@gabors The annotations are due to the fact that |
|
@Zandor300 Can we merge this and make a Swift 6 compatible release soon? Swift 6 is becoming a real thing and Swift concurrency is important already. |
|
@Zandor300 Could we get a review and potential merge of this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Swift 6 as well as enables strict concurrency in the project.
Appropriate annotations have been added to properties/method that access actor-isolated APIs and
Sendableconformances have been added to types provided by the library (e.g.Device,Device.BatterState, etc.)