Nathan Ridge

Thanks. So there are two issues here: 1. The semantic token type which clangd sends for the constructor and destructor tokens is `class` (this is why it gets colored the...

Note that clangd does attach a distinct **modifier** called `constructorOrDestructor` to the semantic tokens for the constructor and destructor. So, it is possible to get vscode to color them differently...

(I've moved the issue to the clangd repo since the change discussed in the issue title needs to be made in the clangd server.)

> And another problem is the color of operators `delete` and `new` are also incorrect. I think the color of `delete` and `new` should be the same as `[]`. I'll...

I assume `CMakeFiles\\main.dir\\main.cpp.obj.modmap` refers to a file. Can you share its contents?

> **Removing `@CMakeFiles\\main.dir\\main.cpp.obj.modmap` from `compile_commands.json` fixes the problem.** Can you show a log of this working case?

In the non-working case the log shows: > I[13:12:06.345] ASTWorker building file C:\Users\luke\Developer\optional\main.cpp version 0 with command [C:/Users/luke/Developer/optional/build] "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.39.33519\\bin\\Hostx64\\x64\\cl.exe" --driver-mode=cl /nologo /DWIN32 /D_WINDOWS /W3 /GR /EHsc /MDd...

A workaround could be to try to add back the `-std:c++latest` flag using the [config file](https://clangd.llvm.org/config.html#compileflags).

I can reproduce this, but I don't think it's an issue in vscode-clangd or the clangd server. The only involvement clangd has in this process is that the clangd server...

For good measure, I did double check that in a simple scenario where I open a source file with one #include and then click on the #include, clangd only gets...