Fix compilation on Xcode 27 by using .disableWarning instead of .unsafeFlags - #5
Open
tcwalther wants to merge 2 commits into
Open
Fix compilation on Xcode 27 by using .disableWarning instead of .unsafeFlags#5tcwalther wants to merge 2 commits into
tcwalther wants to merge 2 commits into
Conversation
…Flags. Updates build system to 6.2.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using .unsafeFlags is no longer allowed in swift packages in Xcode 27. To fix this, I replaced it with .disableWarning calls. These were only introduced in the 6.2 build system, which by default opts in to the new Swift Concurrency. Instead of disabling modern Swift Concurrency checks, I decided to base my PR on #4 instead. After #4 is merged, the only new changes in this PR are to
Package.swift.