@Florian Diebold you might like this:
Lol, it's even recursive. Didn't expect that
That's awesome !
Does it highlight the code inside of string literals?
yup, if the literal is a an argument to the function, whose corresponding parameter is named
We could kinda reserve the special number of hashes
#, e.g. 3 of them to denote a rust source code string literal
we'll use attrs once they are stable: https://github.com/rust-analyzer/rust-analyzer/pull/3349#issuecomment-592022476
Hmm, yeah really, that's a nice application of the attributes!
But I think the current solution is fine. Nobody will know.
there's one intentional Easter egg in rust-analyzer....
Hmm, gonna read all da code to find it!
Does the following still work, @matklad ?
env RUST_LOG=gen_lsp_server=trace code .
I would like to enable
trace logging for
Run extension debug configurations in VSCode...
rust-analyzer.trace.server = verbose is better
Hi all I'm currently trying to debug this issue https://github.com/rust-analyzer/rust-analyzer/issues/4202 but when I inspect with vscode I don't have the part about semantic token type. I think it's because I don't really use rust-analyzer for my syntax highlighting ? Can you give me a tips to enable this kind of view with the syntax highlighting coming from ra ?
Sorry for the noise I find the solution. I just had to select a default theme (dark +) for example
do you have
editor.semanticTokens = true; or something like that in settings.json?
I thin it is required to enable highlighting
I think it's enabled by default now -- it was the theme.
I'd just like to say kudos for implementing it in the rust-analyzer - I believe that's the feature I missed most in the IDE environment. Just switching to rust-analyzer in the extension makes a big difference and I'm excited for the feature :tada:
This is so much faster in today's vscode release