The highlight on vscode seems be wrong

[ws2bhhh]

cland version: 16.0.2
I write some code in C++. This problem won't happend when I changed the file type to .c
Wrong highlight at Line 151, Line 162

[HighCommander4]

I think that's likely to be an issue with client-side highlighting or another extension.

To be sure, can you try disabling the clangd plugin and seeing what the highlighting looks like then?

[ws2bhhh]

After disable clangd plugin:

[ws2bhhh]

Progress: this seems to have been fixed after removing the .clang-tidy file.
Progress: Instead of deleting .clang-tidy, removing "modernize-*," from .clang-tidy seems to fix the problem.
.clang-tidy:
clang-tidy.txt

[HighCommander4]

Interesting. I wonder if your editor is configured to style diagnostic range with a foreground color rather than the more typical squiggly underline.

If you enable the modernize-* diagnostics, are there diagnostics issues for the affected lines (such as that else token)? You should be able to check by hovering over the token, the hover should show the diagnostic if there is one.

[ws2bhhh]

I am not configured to style the diagnostic range with a foreground color.

With modernized-* diagnostics enabled, everything behaves normally. More specifically, all hover->diagnostics behaves normally, except for incorrect highlighting.

[ws2bhhh]

I'm afraid that's as far as it goes. It appears to be just a random, low impact failure. I tried to give minimal reproducible code, but none of them had a similar problem.
Using a lot of C code by extern "C" as in "test2.cpp" above did not succeed in reproducing a similar problem.
Attempts to reduce the total amount of code in "test2.cpp" were also unsuccessful, as I was unable to eliminate irrelevant parts ("test2.cpp" uses easyX, a C++ only graphic library, and uses mostly C code for the main logic).
When deleting code from "test2.cpp", the error-highlighted positions change slightly (even if some empty lines are removed).

[HighCommander4]

One diagnostic technique that could shed some light is: with the editor caret over an incorrectly highlighted token, run the vscode command "Developer: Inspect Editor Tokens and Scopes". That will show a popup with various information related to coloring, feel free to post a screenshot of that.