Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 37562 Build 37561: arc lint + arc unit
Event Timeline
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
37 | NIT: uncapitalize and use 'macro expansions' instead of `Macro Expansions' | |
470 | Is there a place on the internet with conventional textmate scope names? | |
clang-tools-extra/clangd/unittests/SemanticHighlightingTests.cpp | ||
394–395 | Similar to how we highlight everything else, we should also highlight macro declarations and usages (i.e. expansions in the same way). #define $Macro[[DEF_CLASS]](T) class T T{} $Macro[[DEF_CLASS]](A); |
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
470 | This is not standard TX scope names, we only have guidelines. In general, we use the names using in vscode as references (you could see the TM name via vscode's "Insepct TM Scopes" functionality) | |
clang-tools-extra/clangd/unittests/SemanticHighlightingTests.cpp | ||
394–395 | +1, I think we could name the HighlightingKind as Macro instead of MacroExpansion (even through we don't highlighting the macro def yet). |
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
470 | This is from the vscode c++ extension. (we mostly use the same scopes as in that extension, but in a few cases we have our own scopes as there aren't any in vscode) | |
clang-tools-extra/clangd/unittests/SemanticHighlightingTests.cpp | ||
394–395 | We don't seem to collect information about where macro declarations are in the code in ParsedAST. |
LGTM from my side.
clang-tools-extra/clangd/SemanticHighlighting.cpp | ||
---|---|---|
470 | I'd drop the expansion, just use entity.name.function.preprocessor.cpp. |
NIT: uncapitalize and use 'macro expansions' instead of `Macro Expansions'