Also sort the list to make it easier to verify with the implementation
code.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang-tools-extra/clangd/IncludeFixer.cpp | ||
---|---|---|
71 | nit: maybe revert this change, or put err_incomplete_type to the last position to make the list alphabetically ordered. | |
clang-tools-extra/clangd/unittests/DiagnosticsTests.cpp | ||
710 | should this be $type[[a]] ? | |
711 | i don't follow what we gain by this change? | |
715 | why do we need c++17 ? | |
737 | can you move this back to original position ? |
clang-tools-extra/clangd/unittests/DiagnosticsTests.cpp | ||
---|---|---|
710 | yeah, but this is the actual diagnostic range, though it is wired. | |
715 | The newly-added test case is using C++17 feature (structure binding), needs this flag to suppress a diagnostic warning. | |
737 | yeah, I reordered the list. there are two orders: the one listed here, and the one listed in IncludeFixer.cpp. The motivation is to make them aligned, so that it would be easier to compare and spot the difference. The current state is not friendly to readers. |
still LGTM
clang-tools-extra/clangd/unittests/DiagnosticsTests.cpp | ||
---|---|---|
715 | ah okay i see it now, structured binding wasn't obvious from the test case above (i thought there was a typo :D | |
737 | i don't think the orderings in the source vs test is that relevant, but SGTM if it helps you. mainly because:
|
clang-tools-extra/clangd/unittests/DiagnosticsTests.cpp | ||
---|---|---|
737 | yeah, it does help me, especially when I start adding more diagnostics. |
nit: maybe revert this change, or put err_incomplete_type to the last position to make the list alphabetically ordered.