vbvictor wrote: > There are checks that don't require any specific standard, there it would > make sense to keep whatever the default is.
But this could also backfire for users that use "old" c++11. Imagine if the default standard is increased in `check_clang_tidy.py`, then the people who develop checks (and write tests) will unintentionally use c++14 as the default mode. Matchers written with c++14 in mind, may not work in c++11 (I encountered such behavior while developing checks). So the `clang-tidy` users with `std=c++11` will see that the check doesn't work. https://github.com/llvm/llvm-project/pull/158196 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
