Do not block SourceKit-LSP functionality when a build server takes long to initialize #2311
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.
We previously waited for the initialization response from the build server during the creation of a
Workspace
so that we could create aSemanticIndexManager
with the index store path etc. that was returned by thebuild/initialize
response. This caused all functionality (including syntactic) of SourceKit-LSP to be blocked until the build server was initialized.Change the computation of the
SemanticIndexManager
and related types to happen in the background so that we can provide functionality that doesn’t rely on the build server immediately.Fixes #2304