Bogus 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:

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…

All of these are completely bogus in this context. For example, box~ expands to Box::new. The result of applying it is:

fn main() {
    let s = String::new();
    s.Box::new
}

This isn't even valid syntax. These snippets suggestions are completely ignoring context (are they a new feature? I've never seen them before), and add a lot of noise. In most situations, actually valid suggestions are buried behind a bunch of suggestions that don't make sense.

In these situations, snippets should not be suggested; contextual suggestions (like methods on the String type) should be the only suggestions.

[ChayimFriedman2]

I cannot reproduce in VSCode, so this is probably something about your LSP client not properly supporting snippets.

[WhyNotHugo]

It's the LSP which sends the bogus auto-completion suggestions in this context.

What exactly do you mean by "properly supporting snippets"?

[ChayimFriedman2]

It's the LSP which sends the bogus auto-completion suggestions in this context.

Did you check the response manually? What is it? Given it works in VSCode I suspect it's not the case.

What exactly do you mean by "properly supporting snippets"?

I dunno, not properly implementing them or something.

[flodiebold]

These are postfix snippets. When you select e.g. the box snippet, it should expand to Box::new(s), not s.Box::new. These are only sent if your client indicates it supports snippets, in which case it should be able to correctly expand them (not give the result that you posted). If you don't like them, you can turn them off with rust-analyzer.completion.postfix.enable though. (Also, where they show up in the completion list is also significantly controlled by the client. They shouldn't usually show up as the first results.)