-
Notifications
You must be signed in to change notification settings - Fork 321
Rename build system to build server in most cases #2201
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
|
@swift-ci Please test |
2320a9b to
38bbd8d
Compare
|
@swift-ci Please test |
|
@swift-ci Please test Windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would you feel about waiting until ~August for this change to reduce churn between main and 6.2?
| /// The details necessary to create a `BuildServerAdapter`. | ||
| package struct BuildServerSpec { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is a little weird given buildServer is one of the options 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I’ll rename the buildServer case to externalBuildServer.
|
|
||
| /// A type that outwardly acts as a BSP build server and internally uses a `BuiltInBuildSystem` to satisfy the requests. | ||
| actor BuiltInBuildSystemAdapter: QueueBasedMessageHandler { | ||
| /// A type that outwardly acts as a BSP build server and internally uses a `BuiltInBuildServer` to satisfy the requests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like BuiltInBuildServer really is still BuiltInBuildSystem right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I think BuiltInBuildServer makes sense because it’s essentially a BSP server that is built into SourceKit-LSP.
38bbd8d to
901804f
Compare
901804f to
87361af
Compare
|
@swift-ci Please test |
The term *build system* predated our wide-spread adoption of BSP for communicating between SourceKit-LSP to the build system and was never really the correct term anyway – ie. a `JSONCompilationDatabaseBuildSystem` never really sounded right. We now have a correct term for the communication layer between SourceKit-LSP: A build server. Rename most occurrences of *build system* to *build server* to reflect this. There are unfortunately a couple lingering instances of *build system* that we can’t change, most notably: `fallbackBuildSystem` in the config file, the `workspace/waitForBuildSystemUpdates` BSP extension request and the `synchronize-for-build-system-updates` experimental feature.
87361af to
7f4f92e
Compare
|
@swift-ci Please test |
|
@swift-ci Please test Windows |
The term build system predated our wide-spread adoption of BSP for communicating between SourceKit-LSP to the build system and was never really the correct term anyway – ie. a
JSONCompilationDatabaseBuildSystemnever really sounded right. We now have a correct term for the communication layer between SourceKit-LSP: A build server. Rename most occurrences of build system to build server to reflect this. There are unfortunately a couple lingering instances of build system that we can’t change, most notably:fallbackBuildSystemin the config file, theworkspace/waitForBuildSystemUpdatesBSP extension request and thesynchronize-for-build-system-updatesexperimental feature.