I would add that adding lots of checks can cause clang-tidy to have serious performance problems. The software I'm working on is safety-critical. I enabled eve

I would add that adding lots of checks can cause clang-tidy to have serious performance problems. The software I'm working on is safety-critical. I enabled every relevant checker relevant for certificates and tons of additional checkers related to usability and readability. clang-tidy now takes 3x the time it takes to compile :S I ended up splitting off a few checkers in particular into their own separate job. Some checkers are also quite broken. bugprone-unchecked-optional-access is very broken. It caused hangs, it caused crashes, it caused out-of-memory issues. Fortunately, our use of std::optional can mostly be refactored away but doing so is a significant change in the codebase.