Jonathan Grynspan
Jonathan Grynspan
The circular dependency still exists.
Now build the toolchain from source. :)
It would prevent using Swift Testing as a package. Although Swift Testing is in the toolchain today, the core team is interested in moving it to a package in the...
You're describing what's called a "cross-import overlay". We've recently enabled support for these modules when building test targets with `swift test` and `swift build --build-tests`, and it would (I think)...
Or perhaps they should be excluded from `.text`. Not sure the ideal approach here, but having to manually filter them is slowly driving me to madness. :)
Oh, sure—I am maybe fixating on a specific technical solution here. Feel free to come up with a better idea! :)
What you should do is fork the repository (via GitHub) to your account, then move the branch to your fork. From there, GitHub will let you open a PR back...
Can you file an issue against the Swift repo about that oversight? Thanks! 😄
If you do land this change, I'd like to get it cherry-picked to 600 so we can adopt it in swift-testing sooner.
swift-testing should generally be able to adopt swift-syntax-600 features once the release is tagged; swift-syntax-610, speculatively, would be quite a ways off.