Move CI to Swift 5.9 / Xcode 15 beta #1356
Merged
Conversation
This file contains 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
johnfairh
force-pushed
the
jf-ci-swift59
branch
from
ac34069
to
b00a6cc
Compare
|
GitHub actions finally moved past Xcode15 beta 1 so can get on with 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.
Move to Swift 5.9 so I can get tests written for 5.9 features while I have the time.
Specs changes:
realm objc
libdispatchtypes not being translated from their ObjC names into their Swift names.Visible in Xcode 15b2 as well. Something wrong with the macos SDK in Xcode 15, works fine using Swift 5.9 against a 14.3 sysroot.
moya/siesta
no such module
AppKit/UIKit.UIImagereports.This is due to a Swift 5.9 SourceKit change — if we request cursorinfo for a symbol excluded from compilation by eg.
#if os(iOS)then Swift attempts to compile that branch of the#ifa bit harder than earlier, which fails. Does not affect the actual sourcekit behaviour.symgraph
Better treatment of
@spideclarations. Things have moved around because previously these things didn’t even get locations; now we know where they should go.