s-pratik created this revision. s-pratik added a reviewer: aaron.ballman. Herald added a subscriber: arphaman. Herald added a reviewer: njames93. Herald added a project: All. s-pratik requested review of this revision. Herald added a project: clang-tools-extra.
There were some dead links in Suppressing Undesired Diagnostics which i replaced with the working links Repository: rG LLVM Github Monorepo https://reviews.llvm.org/D142377 Files: clang-tools-extra/docs/clang-tidy/index.rst Index: clang-tools-extra/docs/clang-tidy/index.rst =================================================================== --- clang-tools-extra/docs/clang-tidy/index.rst +++ clang-tools-extra/docs/clang-tidy/index.rst @@ -306,13 +306,13 @@ adhere to a coding standard, or is otherwise problematic in some way. However, if the code is known to be correct, it may be useful to silence the warning. Some clang-tidy checks provide a check-specific way to silence the diagnostics, -e.g. `bugprone-use-after-move <checks/bugprone-use-after-move.html>`_ can be +e.g. `bugprone-use-after-move <checks/bugprone/use-after-move.html>`_ can be silenced by re-initializing the variable after it has been moved out, `bugprone-string-integer-assignment -<checks/bugprone-string-integer-assignment.html>`_ can be suppressed by +<checks/bugprone/string-integer-assignment.html>`_ can be suppressed by explicitly casting the integer to ``char``, `readability-implicit-bool-conversion -<checks/readability-implicit-bool-conversion.html>`_ can also be suppressed by +<checks/readability/implicit-bool-conversion.html>`_ can also be suppressed by using explicit casts, etc. If a specific suppression mechanism is not available for a certain warning, or
Index: clang-tools-extra/docs/clang-tidy/index.rst =================================================================== --- clang-tools-extra/docs/clang-tidy/index.rst +++ clang-tools-extra/docs/clang-tidy/index.rst @@ -306,13 +306,13 @@ adhere to a coding standard, or is otherwise problematic in some way. However, if the code is known to be correct, it may be useful to silence the warning. Some clang-tidy checks provide a check-specific way to silence the diagnostics, -e.g. `bugprone-use-after-move <checks/bugprone-use-after-move.html>`_ can be +e.g. `bugprone-use-after-move <checks/bugprone/use-after-move.html>`_ can be silenced by re-initializing the variable after it has been moved out, `bugprone-string-integer-assignment -<checks/bugprone-string-integer-assignment.html>`_ can be suppressed by +<checks/bugprone/string-integer-assignment.html>`_ can be suppressed by explicitly casting the integer to ``char``, `readability-implicit-bool-conversion -<checks/readability-implicit-bool-conversion.html>`_ can also be suppressed by +<checks/readability/implicit-bool-conversion.html>`_ can also be suppressed by using explicit casts, etc. If a specific suppression mechanism is not available for a certain warning, or
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
