Eugene.Zelenko created this revision. Eugene.Zelenko added a reviewer: alexfh. Eugene.Zelenko added a subscriber: cfe-commits. Eugene.Zelenko set the repository for this revision to rL LLVM.
Checks are described at beginning and directory names follow name prefixes, so another list is redundant. Repository: rL LLVM https://reviews.llvm.org/D23596 Files: docs/clang-tidy/index.rst Index: docs/clang-tidy/index.rst =================================================================== --- docs/clang-tidy/index.rst +++ docs/clang-tidy/index.rst @@ -341,27 +341,8 @@ Next, you need to decide which module the check belongs to. If the check verifies conformance of the code to a certain coding style, it probably deserves -a separate module and a directory in ``clang-tidy/``. There are already modules -implementing checks related to: +a separate module and a directory in ``clang-tidy/``. -* `C++ Core Guidelines - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cppcoreguidelines/>`_ -* `CERT Secure Coding Standards - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cert/>`_ -* `Google Style Guide - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/google/>`_ -* `LLVM Style - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/llvm/>`_ -* `modernizing C/C++ code - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/modernize/>`_ -* potential `performance problems - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/performance/>`_ -* various `readability issues - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/readability/>`_ -* and `miscellaneous checks - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/misc/>`_ - that we couldn't find a better category for. - After choosing the module, you need to create a class for your check: .. code-block:: c++
Index: docs/clang-tidy/index.rst =================================================================== --- docs/clang-tidy/index.rst +++ docs/clang-tidy/index.rst @@ -341,27 +341,8 @@ Next, you need to decide which module the check belongs to. If the check verifies conformance of the code to a certain coding style, it probably deserves -a separate module and a directory in ``clang-tidy/``. There are already modules -implementing checks related to: +a separate module and a directory in ``clang-tidy/``. -* `C++ Core Guidelines - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cppcoreguidelines/>`_ -* `CERT Secure Coding Standards - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/cert/>`_ -* `Google Style Guide - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/google/>`_ -* `LLVM Style - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/llvm/>`_ -* `modernizing C/C++ code - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/modernize/>`_ -* potential `performance problems - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/performance/>`_ -* various `readability issues - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/readability/>`_ -* and `miscellaneous checks - <http://reviews.llvm.org/diffusion/L/browse/clang-tools-extra/trunk/clang-tidy/misc/>`_ - that we couldn't find a better category for. - After choosing the module, you need to create a class for your check: .. code-block:: c++
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
