No semantic tokens for many keywords

[HoldMyBeer1111]

Hi, why do some keywords (eg for) have Semantic Tokens, but others dont? Any ideas?

:Inspect for for

:Inspect for let

[mrcjkb]

Hey 👋

that would be a rust-analyzer question.

I think many LSP servers don't provide semantic tokens for all keywords.

[mrcjkb]

then it's likely either

• Your colorscheme not supporting all tokens.
• Use of different rust-analyzer builds in Neovim and VSCode.

[HoldMyBeer1111]

• Your colorscheme not supporting all tokens.

wdym? I have vim.api.nvim_set_hl(0, '@lsp.type.keyword.rust', { fg = '#d3869b' }) in a config file, and it doesnt work because some keywords lack semantic tokens from LSP. Looks like nothing to do with a colorscheme.

• Use of different rust-analyzer builds in Neovim and VSCode.

I have checked with the same binary.
vscode

neovim

[mrcjkb]

Can you confirm that the highlighting of the let keyword in VSCode in fact comes from rust-analyzer and is not part of VSCode's theming?
The documentation, the texmate scopes listed in your screenshot, and this file, lead me to believe that might not be the case.
In VSCode, "semantic token" is not necessarily synonymous with LSP semantic tokens.

rustaceanvim doesn't implement any highlighting or theming, which is out of scope for this plugin.

[HoldMyBeer1111]

let is colored differently and does not have a "semantic token type" if rust-analyzer extension is disabled.

[mrcjkb]

Then I suggest asking in the rust-analyzer discussions. It could be a non-standard token that isn't supported by Neovim or a server configuration issue.

As I said, highlighting is out of scope for rustaceanvim.