Remove print-init
subcommand from swift-parser-cli
#908
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.
debugInitCall
, which is the backbone ofswift-parser-cli
is defined in_SwiftSyntaxTestSupport
, which links against XCTest. Ifswift-parser-cli
links against_SwiftSyntaxTestSupport
, it also links againstXCTest
, causing its execution to fail with a dyld error outside of Xcode.The solution would be to move
debugInitCall
into a new module thatswift-parser-cli
can link against but IMHO theprint-init
subcommand doesn’t provide sufficent value for that since you most likely want to use it in test cases where you can use a debugger command to get thedebugInitCall
result:e print(tree.debugInitCall)
.