[SwiftSyntax] Add CMake argument to enable assertions in SwiftSyntax for Release+Assert builds #64572
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
Member
Author
|
@swift-ci Please smoke test |
rintaro
approved these changes
Mar 23, 2023
…for Release+Assert builds This does not do anything by itself, it needs a corresponding change in swift-syntax to pick up the CMake option and actually enable assertions.
ahoppen
force-pushed
the
ahoppen/swiftsyntax-assertions
branch
from
1a3a809 to
d38bd10
Compare
Member
Author
|
@swift-ci Please smoke test |
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.
This does not do anything by itself, it needs a corresponding change in swift-syntax to pick up the CMake option and actually enable assertions.