Automerge: [clang-tidy][docs][NFC] Enforce 80 characters limit (3/N) (#167830)

Fix documentation in `hicpp`, `linuxkernel`, `llvm`, `llvmlibc`, `misc`
and `modernize`.

This is part of the codebase cleanup described in
llvm/llvm-project#167098

Author: zeyi2

clang-tools-extra/docs/clang-tidy/checks/hicpp/braces-around-statements.rst

@@ -6,6 +6,8 @@ hicpp-braces-around-statements
 ==============================
 
 The `hicpp-braces-around-statements` check is an alias, please see
-:doc:`readability-braces-around-statements <../readability/braces-around-statements>`
+:doc:`readability-braces-around-statements
+<../readability/braces-around-statements>`
 for more information.
-It enforces the `rule 6.1.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/statements>`_.
+It enforces the `rule 6.1.1
+<https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/statements>`_.

clang-tools-extra/docs/clang-tidy/checks/hicpp/explicit-conversions.rst

@@ -5,13 +5,21 @@
 hicpp-explicit-conversions
 ==========================
 
-This check is an alias for :doc:`google-explicit-constructor <../google/explicit-constructor>`.
-Used to enforce parts of `rule 5.4.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard-expressions>`_.
-This check will enforce that constructors and conversion operators are marked `explicit`.
-Other forms of casting checks are implemented in other places.
-The following checks can be used to check for more forms of casting:
+This check is an alias for
+:doc:`google-explicit-constructor <../google/explicit-constructor>`.
 
-- :doc:`cppcoreguidelines-pro-type-static-cast-downcast <../cppcoreguidelines/pro-type-static-cast-downcast>`
-- :doc:`cppcoreguidelines-pro-type-reinterpret-cast <../cppcoreguidelines/pro-type-reinterpret-cast>`
-- :doc:`cppcoreguidelines-pro-type-const-cast <../cppcoreguidelines/pro-type-const-cast>`
-- :doc:`cppcoreguidelines-pro-type-cstyle-cast <../cppcoreguidelines/pro-type-cstyle-cast>`
+Used to enforce parts of `rule 5.4.1
+<https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard-expressions>`_.
+This check will enforce that constructors and conversion operators are
+marked ``explicit``. Other forms of casting checks are implemented in
+other places. The following checks can be used to check for more forms
+of casting:
+
+- :doc:`cppcoreguidelines-pro-type-static-cast-downcast
+  <../cppcoreguidelines/pro-type-static-cast-downcast>`
+- :doc:`cppcoreguidelines-pro-type-reinterpret-cast
+  <../cppcoreguidelines/pro-type-reinterpret-cast>`
+- :doc:`cppcoreguidelines-pro-type-const-cast
+  <../cppcoreguidelines/pro-type-const-cast>`
+- :doc:`cppcoreguidelines-pro-type-cstyle-cast
+  <../cppcoreguidelines/pro-type-cstyle-cast>`

clang-tools-extra/docs/clang-tidy/checks/hicpp/function-size.rst

@@ -5,7 +5,8 @@
 hicpp-function-size
 ===================
 
-This check is an alias for :doc:`readability-function-size <../readability/function-size>`.
+This check is an alias for
+:doc:`readability-function-size <../readability/function-size>`.
 Useful to enforce multiple sections on function complexity.
 
 - `rule 8.2.2 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/definitions>`_

clang-tools-extra/docs/clang-tidy/checks/hicpp/ignored-remove-result.rst

@@ -13,7 +13,8 @@ operating over. On completion, they return an iterator to the last valid
 element. In the majority of cases the correct behavior is to use this result as
 the first operand in a call to ``std::erase``.
 
-This check is a subset of :doc:`bugprone-unused-return-value <../bugprone/unused-return-value>`
+This check is a subset of :doc:`bugprone-unused-return-value
+<../bugprone/unused-return-value>`
 and depending on used options it can be superfluous to enable both checks.
 
 Options

clang-tools-extra/docs/clang-tidy/checks/hicpp/invalid-access-moved.rst

@@ -5,6 +5,7 @@
 hicpp-invalid-access-moved
 ==========================
 
-This check is an alias for :doc:`bugprone-use-after-move <../bugprone/use-after-move>`.
+This check is an alias for
+:doc:`bugprone-use-after-move <../bugprone/use-after-move>`.
 
 Implements parts of the `rule 8.4.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/definitions>`_ to check if moved-from objects are accessed.

clang-tools-extra/docs/clang-tidy/checks/hicpp/move-const-arg.rst

@@ -6,5 +6,6 @@ hicpp-move-const-arg
 ====================
 
 The `hicpp-move-const-arg` check is an alias, please see
-:doc:`performance-move-const-arg <../performance/move-const-arg>` for more information.
+:doc:`performance-move-const-arg <../performance/move-const-arg>`
+for more information.
 It enforces the `rule 17.3.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/standard-library>`_.

clang-tools-extra/docs/clang-tidy/checks/hicpp/multiway-paths-covered.rst

@@ -4,15 +4,16 @@ hicpp-multiway-paths-covered
 ============================
 
 This check discovers situations where code paths are not fully-covered.
-It furthermore suggests using ``if`` instead of ``switch`` if the code will be more clear.
+It furthermore suggests using ``if`` instead of ``switch`` if the code
+will be more clear.
 The `rule 6.1.2 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/statements>`_
 and `rule 6.1.4 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/statements>`_
 of the High Integrity C++ Coding Standard are enforced.
 
-``if-else if`` chains that miss a final ``else`` branch might lead to unexpected
-program execution and be the result of a logical error.
-If the missing ``else`` branch is intended you can leave it empty with a clarifying
-comment.
+``if-else if`` chains that miss a final ``else`` branch might lead to
+unexpected program execution and be the result of a logical error.
+If the missing ``else`` branch is intended you can leave it empty with
+a clarifying comment.
 This warning can be noisy on some code bases, so it is disabled by default.
 
 .. code-block:: c++
@@ -28,7 +29,8 @@ This warning can be noisy on some code bases, so it is disabled by default.
      // ...
   }
 
-Similar arguments hold for ``switch`` statements which do not cover all possible code paths.
+Similar arguments hold for ``switch`` statements which do not cover all
+possible code paths.
 
 .. code-block:: c++
 

clang-tools-extra/docs/clang-tidy/checks/hicpp/named-parameter.rst

@@ -5,6 +5,7 @@
 hicpp-named-parameter
 =====================
 
-This check is an alias for :doc:`readability-named-parameter <../readability/named-parameter>`.
+This check is an alias for :doc:`readability-named-parameter
+<../readability/named-parameter>`.
 
 Implements `rule 8.2.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/definitions>`_.

clang-tools-extra/docs/clang-tidy/checks/hicpp/no-array-decay.rst

@@ -6,6 +6,7 @@ hicpp-no-array-decay
 ====================
 
 The `hicpp-no-array-decay` check is an alias, please see
-:doc:`cppcoreguidelines-pro-bounds-array-to-pointer-decay <../cppcoreguidelines/pro-bounds-array-to-pointer-decay>`
+:doc:`cppcoreguidelines-pro-bounds-array-to-pointer-decay
+<../cppcoreguidelines/pro-bounds-array-to-pointer-decay>`
 for more information.
 It enforces the `rule 4.1.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/standard-conversions>`_.

clang-tools-extra/docs/clang-tidy/checks/hicpp/uppercase-literal-suffix.rst

@@ -6,7 +6,8 @@ hicpp-uppercase-literal-suffix
 ==============================
 
 The hicpp-uppercase-literal-suffix check is an alias, please see
-:doc:`readability-uppercase-literal-suffix <../readability/uppercase-literal-suffix>` for more information.
+:doc:`readability-uppercase-literal-suffix
+<../readability/uppercase-literal-suffix>` for more information.
 
 Partially implements `rule 4.2.1 <https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard/standard-conversions>`_
 to ensure that the ``U`` suffix is writeln properly.