Backport of rust-analyzer "Use completion item indices instead of property matching"#132987
Merged
bors merged 2 commits intorust-lang:betafrom Nov 16, 2024
Merged
Backport of rust-analyzer "Use completion item indices instead of property matching"#132987bors merged 2 commits intorust-lang:betafrom
bors merged 2 commits intorust-lang:betafrom
Conversation
…ng for the completion item to resolve
Collaborator
|
rustbot
added
the
S-waiting-on-review
Collaborator
|
rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
Member
|
cc ... @cuviper? |
Member
|
This probably needs T-release signoff... r? release |
rustbot
added
the
T-release
Member
|
It's fine with me if the team approves, which I assume so since @lnicola is a member. Feel free to Usually we'd go through nominated/accepted labels and then let the release team backport it ourselves, but we don't really have a way to do that labeling for subtree projects. |
Merged
Member
rustbot
added
the
beta-accepted
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Nov 15, 2024
[beta] backports - Use completion item indices instead of property matching rust-lang#132987, rust-lang/rust-analyzer#18503 - Reject raw lifetime followed by `'`, like regular lifetimes do rust-lang#132341 - Only disable cache if predicate has opaques within it rust-lang#132625 - rustdoc-search: case-sensitive only when capitals are used rust-lang#133043 r? cuviper
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Nov 16, 2024
[beta] backports - Use completion item indices instead of property matching rust-lang#132987, rust-lang/rust-analyzer#18503 - Reject raw lifetime followed by `'`, like regular lifetimes do rust-lang#132341 - Only disable cache if predicate has opaques within it rust-lang#132625 - rustdoc-search: case-sensitive only when capitals are used rust-lang#133043 - (ci) Update macOS Xcode to 15 rust-lang#131570 r? cuviper
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
CC rust-lang/rust-analyzer#18503
CC @SomeoneToIgnore
This fixes a problem that occurs on less-conforming LSP clients like Kate and Emacs
lsp-mode.r? @traviscross