Contextually irrelevant snippet completions suggested

[WhyNotHugo]

> rust-analyzer --version
rust-analyzer 2025.05.19
> rustc -V
rustc 1.87.0 (17067e9ac 2025-05-09) (Alpine Linux 1.87.0-r0)
> nvim --version
NVIM v0.11.1
Build type: MinSizeRel
LuaJIT 2.1.1723681758
``

**code snippet to reproduce**:
```rust
fn main() {
    let s = String::new();
    s.
}

Please the cursor at the end of line s. and trigger auto-completion. rust-analyzer suggests a bunch of snippets: let~ letm, ref~, box~, etc…

When using the "expand" shortcut, these snippets are expanded to things like Box::new(s).

These suggestions don't make sense in this context; if I type s., I expect to see completion for associated function calls, not potential re-writes for this.

The main issue at hand, is that these suggestions (about a dozen) drown out the actually relevant suggestions; one that are consistent to what I've just typed.

These suggestions should only be shown when they are consistent with what one has typed in the code editor.

---

Somewhat related to #19906, which derailed due to a tangential detail, then locked and my last reply silently discarded.

[ChayimFriedman2]

First of all, #19906 wasn't locked - it was just converted into a discussion as "probably not a bug". You are more than welcome to express your opinion at #19967.

---

In VSCode I don't see those snippet suggestion at the top of the completion list (they are quite behind), and we set their score so it should always be the case. Although typing this makes me think... does neovim sorts by sortText in descending order? The LSP specification doesn't specify a sort order, but we assume it'll be ascending.

[flodiebold]

Let's keep the discussion in #19967.

[WhyNotHugo]

First of all, #19906 wasn't locked - it was just converted into a discussion as "probably not a bug". You are more than welcome to express your opinion at #19967.

As an external user, I mostly noticed rust-lang locked and limited conversation to collaborators, and that the comments box was disabled (and my last reply was silently redirected to /dev/null, apparently).

I missed the text under the padlock which indicates that this has been converting into a discussion, my bad. Here's what this looks like for non-contributors:

I'll move discussion onto the issue tracker as #19967