-
Notifications
You must be signed in to change notification settings - Fork 440
Conditionalize Use of New Internal Parsing APIs #752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Provides a weak solution to swiftlang#749 by assuming that the toolchain used to build SwiftSyntax is also the toolchain you're linking the internal syntax dylib out of.
@swift-ci test |
With Xcode 14 RC 1 the |
Good point. I'll just drop the gates entirely and we'll shadow these APIs for good. |
Xcode 14 RC1 ships with a Swift standard library that is too old to contain these primitives despite the compiler version being new. Just drop the gates - we can shadow these APIs in these files just fine.
@swift-ci test |
This compiles with Xcode 14 RC 1 but needs to find a |
@swift-ci test |
Yes, for that you will need to use a recent swift development snapshot. |
Does this need to be cherry-picked onto the |
I believe this needs to be applied onto |
Provides a weak solution to #749 by assuming that the toolchain used to build SwiftSyntax is also the toolchain you're linking the internal syntax dylib out of.
@jpsim