Tool results are deduplicated by the result key.
Details
Diff Detail
- Repository
- rC Clang
Event Timeline
LGTM.
| include/clang/Tooling/AllTUsExecution.h | ||
|---|---|---|
| 35 | consider using a default parameter (= 0)? use the llvm::hardware_concurrency by default, and you don't have to pass the 0 in the unittest. | |
| lib/Tooling/AllTUsExecution.cpp | ||
| 158 | also document all results are stored in memory, the result size should be suitable to be loaded in memory. | |
| unittests/Tooling/ExecutionTest.cpp | ||
| 264 | nit: ++i. | |
Address review comments.
| include/clang/Tooling/AllTUsExecution.h | ||
|---|---|---|
| 35 | The constructors aren't usually used directly (outside of unit tests; interface design shouldn't be driven by tests), so I didn't use default parameters, since they are usually disliked... | |
| unittests/Tooling/ExecutionTest.cpp | ||
| 264 | Done. (I don't think this matters for simple types tho...) | |
consider using a default parameter (= 0)? use the llvm::hardware_concurrency by default, and you don't have to pass the 0 in the unittest.