VSCode does not have a scope for enum constants. So they were placed under "constant.other.enum" as that seems to be the most correct scope for enum constants. However, this makes theia color them blue (the same color it uses for keywords).
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
mostly good.
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
122 ↗ | (On Diff #209445) | nit: clang-format. |
257 ↗ | (On Diff #209445) | could you check the tm scope on vscode? They seem to use variable.other.enummember. |
clang-tools-extra/clangd/unittests/SemanticHighlightingTests.cpp | ||
107 ↗ | (On Diff #209445) | since we have a dedicated testcase for enum, could you extend the testcase here? |
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
257 ↗ | (On Diff #209445) | this comment is undone, vscode is using https://github.com/microsoft/vscode/blob/master/extensions/cpp/syntaxes/cpp.tmLanguage.json#L10024 |
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
257 ↗ | (On Diff #209445) | Oh yeah, I was going to write a comment about keeping it as constant.other.enum or something similar to it. Because it's not really a variable. But as we've stuck to the same TM scopes as vscode we should probably keep doing that so I'll change to variable.other.enummember and land. |