|130 ms||linux > Clang-Unit.ASTMatchers/_/ASTMatchersTests::ASTMatchersTest.Finder_DynamicOnlyAcceptsSomeMatchers|
Note: Google Test filter = ASTMatchersTest.Finder_DynamicOnlyAcceptsSomeMatchers [==========] Running 1 test from 1 test case. [----------] Global test environment set-up.
|390 ms||linux > HWAddressSanitizer-x86_64.TestCases::sizes.cpp|
Script: -- : 'RUN: at line 3'; /mnt/disks/ssd0/agent/llvm-project/build/./bin/clang --driver-mode=g++ -m64 -gline-tables-only -fsanitize=hwaddress -fuse-ld=lld -mcmodel=large -mllvm -hwasan-globals -mllvm -hwasan-use-short-granules -mllvm -hwasan-instrument-landing-pads=0 -mllvm -hwasan-instrument-personality-functions /mnt/disks/ssd0/agent/llvm-project/compiler-rt/test/hwasan/TestCases/sizes.cpp -nostdlib++ -lstdc++ -o /mnt/disks/ssd0/agent/llvm-project/build/projects/compiler-rt/test/hwasan/X86_64/TestCases/Output/sizes.cpp.tmp
|60 ms||windows > Clang-Unit.ASTMatchers/_/ASTMatchersTests_exe::ASTMatchersTest.Finder_DynamicOnlyAcceptsSomeMatchers|
Note: Google Test filter = ASTMatchersTest.Finder_DynamicOnlyAcceptsSomeMatchers [==========] Running 1 test from 1 test case.
Thanks for putting this together!
As mentioned on the cfe-dev thread, for our out-of-tree checks we're planning to wrap with traverse() instead, to capture the full matcher logic more locally at the cost of some readability.
So if this won't be used for in-tree checks, we'd probably want to hold off on this unless someone in particular plans to use it.
I don't really get why this would be optional.
Writing to stderr from a library isn't ideal. (e.g. in multithreaded programs - clangd uses a wrapped stderr as its log stream, this bypasses the mutex)