improvement: Improve efficiency of completions #23355
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are two improvements here: - isAbsent(force = false) which is already used in the codebase when we care about performance - we don't search for extension or implicit methods on empty query, as we would have inverseSemanticdb invoked on every possible extension method and it's quite inefficient
rochala
approved these changes
Jun 11, 2025
There was a problem hiding this comment.
Nice,
If we're trying to improve completions performance there is also one change that we could make:
Lsp provides an api to get information what triggered the completions. Based on that we could cache compiler completions and only compute ones from symbol search. Should save some time too
tgodzik
added a commit
to scala/scala3-lts
that referenced
this pull request
Jun 19, 2025
There are two improvements here: - isAbsent(force = false) which is already used in the codebase when we care about performance - we don't search for extension or implicit methods on empty query, as we would have inverseSemanticdb invoked on every possible extension method and it's quite inefficient [Cherry-picked 99543c5]
tgodzik
added a commit
to scala/scala3-lts
that referenced
this pull request
Jun 20, 2025
There are two improvements here: - isAbsent(force = false) which is already used in the codebase when we care about performance - we don't search for extension or implicit methods on empty query, as we would have inverseSemanticdb invoked on every possible extension method and it's quite inefficient [Cherry-picked 99543c5]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are two improvements here: