njames93 added a comment. Can I ask what the motivation is for this change?
You may want to check the actual header files for the checks. A lot of them have a comment saying. /// For the user-facing documentation see: /// http://clang.llvm.org/extra/clang-tidy/checks/bugprone-reserved-identifier.html I'm no expert on the inner workings of search engines, but I feel this will temporarily mess up my go to way of finding out a checks documentation, just googling its name. I wouldn't say its reason for blocking this, just my 0.02$. ================ Comment at: clang-tools-extra/clang-tidy/add_new_check.py:88 /// For the user-facing documentation see: /// http://clang.llvm.org/extra/clang-tidy/checks/%(check_name_dashes)s.html class %(check_name)s : public ClangTidyCheck { ---------------- Again, this comment would need to be updated to use the new directory structure/ CHANGES SINCE LAST ACTION https://reviews.llvm.org/D126495/new/ https://reviews.llvm.org/D126495 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
