PiotrZSL wrote: Problem that I see with "modernize" category is that it overlap with other categories, for example modernize-make-shared is mainly a performance check, modernize-redundant-void-arg is an readability check. We basically lack category for code design (rule of 5, limiting class/file size, complexity), we lack category for security issues (things that are clearly a bug). And we got generic checks in some codding standard categories, that almost every project may need to enable like google-explicit-constructor. If we would have actual check aliases or check tags, so some checks could be target for example with "google" or "cert" tag then it would be different story. But with current speed of delivering changes to clang-tidy, it will never happen.
https://github.com/llvm/llvm-project/pull/72385 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
