Makes use of insertion order to stabilize output for multiple decls.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Unit tests: pass. 61895 tests passed, 0 failed and 782 were skipped.
clang-tidy: unknown.
clang-format: pass.
Build artifacts: diff.json, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
| clang-tools-extra/clangd/FindTarget.cpp | ||
|---|---|---|
| 202 | why two maps vs map to pair<size_t, RelSet> here? Seems a little inefficient/untidy | |
Unit tests: pass. 61912 tests passed, 0 failed and 783 were skipped.
clang-tidy: unknown.
clang-format: pass.
Build artifacts: diff.json, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
| clang-tools-extra/clangd/FindTarget.cpp | ||
|---|---|---|
| 224 | no need for lookups I think Result.resize(Decls.size());
for (auto& Elem : Decls)
Result[Elem.second.second] = {Elem.first, Elem.second.first}; | |
- Get rid of redundant sorting step
| clang-tools-extra/clangd/FindTarget.cpp | ||
|---|---|---|
| 224 | ah right, sorry I was in a rush :/ | |
Unit tests: pass. 61912 tests passed, 0 failed and 783 were skipped.
clang-tidy: unknown.
clang-format: pass.
Build artifacts: diff.json, clang-format.patch, CMakeCache.txt, console-log.txt, test-results.xml
why two maps vs map to pair<size_t, RelSet> here? Seems a little inefficient/untidy