Skip to content

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Oct 6, 2021

Depends on #321.


AFAICT the group info was only used for swift modules built by build-script.py. But since we don’t ship the swift modules as part of the toolchain anymore and the intended way to build SwiftSyntax for clients is through the SwiftPM package, I think the maintainance cost is higher than the value it provides (which I think has always been marginal).

Moving `Diagnostic` etc. to the `SwiftSyntaxParser` module required `swift-format` to import `SwiftSyntaxParser` in a bunch of places where it shouldn’t be needed. Move the types back to the `SwiftSyntax` module for now until we completely refactor the parser to just return `Diagnostics` and not require a `DiagnsoticEngine` (tracked by SR-15280).
AFAICT the group info was only used for swift modules built by `build-script.py`. But since we don’t ship the swift modules as part of the toolchain anymore and the intended way to build SwiftSyntax for clients is through the SwiftPM package, I think the maintainance cost is higher than the value it provides (which I think has always been marginal).
@ahoppen ahoppen marked this pull request as draft October 6, 2021 09:52
@ahoppen
Copy link
Member Author

ahoppen commented Oct 6, 2021

@swift-ci Please test

@akyrtzi
Copy link
Contributor

akyrtzi commented Oct 6, 2021

This has value in contexts where the module files are provided separately.

@ahoppen ahoppen closed this Oct 7, 2021
@ahoppen ahoppen deleted the pr/remove-group-info branch October 7, 2021 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants