[NFC] Trim trailing whitespace in *.rst

Author: Shao-Ce SUN

clang-tools-extra/docs/clang-tidy/checks/abseil-redundant-strcat-calls.rst

@@ -3,7 +3,7 @@
 abseil-redundant-strcat-calls
 =============================
 
-Suggests removal of unnecessary calls to ``absl::StrCat`` when the result is 
+Suggests removal of unnecessary calls to ``absl::StrCat`` when the result is
 being passed to another call to ``absl::StrCat`` or ``absl::StrAppend``.
 
 The extra calls cause unnecessary temporary strings to be constructed. Removing
@@ -21,6 +21,6 @@ Examples:
 
   absl::StrAppend(&s, absl::StrCat("E", "F", "G"));
   //before
-  
+
   absl::StrAppend(&s, "E", "F", "G");
   //after

clang-tools-extra/docs/clang-tidy/checks/abseil-str-cat-append.rst

@@ -3,7 +3,7 @@
 abseil-str-cat-append
 =====================
 
-Flags uses of ``absl::StrCat()`` to append to a ``std::string``. Suggests 
+Flags uses of ``absl::StrCat()`` to append to a ``std::string``. Suggests
 ``absl::StrAppend()`` should be used instead.
 
 The extra calls cause unnecessary temporary strings to be constructed. Removing

clang-tools-extra/docs/clang-tidy/checks/bugprone-bad-signal-to-kill-thread.rst

@@ -3,8 +3,8 @@
 bugprone-bad-signal-to-kill-thread
 ==================================
 
-Finds ``pthread_kill`` function calls when a thread is terminated by 
-raising ``SIGTERM`` signal and the signal kills the entire process, not 
+Finds ``pthread_kill`` function calls when a thread is terminated by
+raising ``SIGTERM`` signal and the signal kills the entire process, not
 just the individual thread. Use any signal except ``SIGTERM``.
 
 .. code-block: c++

clang-tools-extra/docs/clang-tidy/checks/bugprone-not-null-terminated-result.rst

@@ -128,5 +128,5 @@ Options
 .. option::  WantToUseSafeFunctions
 
    The value `true` specifies that the target environment is considered to
-   implement '_s' suffixed memory and string handler functions which are safer 
+   implement '_s' suffixed memory and string handler functions which are safer
    than older versions (e.g. 'memcpy_s()'). The default value is `true`.

clang-tools-extra/docs/clang-tidy/checks/bugprone-reserved-identifier.rst

@@ -5,53 +5,53 @@ bugprone-reserved-identifier
 
 `cert-dcl37-c` and `cert-dcl51-cpp` redirect here as an alias for this check.
 
-Checks for usages of identifiers reserved for use by the implementation. 
+Checks for usages of identifiers reserved for use by the implementation.
 
 The C and C++ standards both reserve the following names for such use:
 
 - identifiers that begin with an underscore followed by an uppercase letter;
 - identifiers in the global namespace that begin with an underscore.
 
 The C standard additionally reserves names beginning with a double underscore,
-while the C++ standard strengthens this to reserve names with a double 
+while the C++ standard strengthens this to reserve names with a double
 underscore occurring anywhere.
 
 Violating the naming rules above results in undefined behavior.
 
 .. code-block:: c++
 
-  namespace NS { 
+  namespace NS {
     void __f(); // name is not allowed in user code
     using _Int = int; // same with this
     #define cool__macro // also this
   }
   int _g(); // disallowed in global namespace only
 
-The check can also be inverted, i.e. it can be configured to flag any 
-identifier that is _not_ a reserved identifier. This mode is for use by e.g. 
-standard library implementors, to ensure they don't infringe on the user 
+The check can also be inverted, i.e. it can be configured to flag any
+identifier that is _not_ a reserved identifier. This mode is for use by e.g.
+standard library implementors, to ensure they don't infringe on the user
 namespace.
 
-This check does not (yet) check for other reserved names, e.g. macro names 
-identical to language keywords, and names specifically reserved by language 
+This check does not (yet) check for other reserved names, e.g. macro names
+identical to language keywords, and names specifically reserved by language
 standards, e.g. C++ 'zombie names' and C future library directions.
 
-This check corresponds to CERT C Coding Standard rule `DCL37-C. Do not declare 
+This check corresponds to CERT C Coding Standard rule `DCL37-C. Do not declare
 or define a reserved identifier
 <https://wiki.sei.cmu.edu/confluence/display/c/DCL37-C.+Do+not+declare+or+define+a+reserved+identifier>`_
 as well as its C++ counterpart, `DCL51-CPP. Do not declare or define a reserved
-identifier 
+identifier
 <https://wiki.sei.cmu.edu/confluence/display/cplusplus/DCL51-CPP.+Do+not+declare+or+define+a+reserved+identifier>`_.
 
 Options
 -------
 
 .. option:: Invert
 
-   If `true`, inverts the check, i.e. flags names that are not reserved. 
+   If `true`, inverts the check, i.e. flags names that are not reserved.
    Default is `false`.
 
 .. option:: AllowedIdentifiers
 
-   Semicolon-separated list of names that the check ignores. Default is an 
+   Semicolon-separated list of names that the check ignores. Default is an
    empty list.

clang-tools-extra/docs/clang-tidy/checks/bugprone-signal-handler.rst

@@ -32,6 +32,5 @@ and has an alias name ``cert-sig30-c``.
   assumable that  the reason is that the list was not updated for C11.
   The checker includes ``quick_exit`` in the set of safe functions.
   Functions registered as exit handlers are not checked.
-  
-  Default is ``POSIX``.
 
+  Default is ``POSIX``.

clang-tools-extra/docs/clang-tidy/checks/bugprone-spuriously-wake-up-functions.rst

@@ -3,9 +3,9 @@
 bugprone-spuriously-wake-up-functions
 =====================================
 
-Finds ``cnd_wait``, ``cnd_timedwait``, ``wait``, ``wait_for``, or 
+Finds ``cnd_wait``, ``cnd_timedwait``, ``wait``, ``wait_for``, or
 ``wait_until`` function calls when the function is not invoked from a loop
-that checks whether a condition predicate holds or the function has a 
+that checks whether a condition predicate holds or the function has a
 condition parameter.
 
 .. code-block: c++

clang-tools-extra/docs/clang-tidy/checks/bugprone-suspicious-enum-usage.rst

@@ -5,11 +5,11 @@ bugprone-suspicious-enum-usage
 
 The checker detects various cases when an enum is probably misused (as a bitmask
 ).
-  
+
 1. When "ADD" or "bitwise OR" is used between two enum which come from different
    types and these types value ranges are not disjoint.
 
-The following cases will be investigated only using :option:`StrictMode`. We 
+The following cases will be investigated only using :option:`StrictMode`. We
 regard the enum as a (suspicious)
 bitmask if the three conditions below are true at the same time:
 
@@ -36,13 +36,13 @@ Examples:
   enum { A, B, C };
   enum { D, E, F = 5 };
   enum { G = 10, H = 11, I = 12 };
-  
+
   unsigned flag;
   flag =
       A |
       H; // OK, disjoint value intervals in the enum types ->probably good use.
   flag = B | F; // Warning, have common values so they are probably misused.
-  
+
   // Case 2:
   enum Bitmask {
     A = 0,
@@ -53,7 +53,7 @@ Examples:
     F = 16,
     G = 31 // OK, real bitmask.
   };
-  
+
   enum Almostbitmask {
     AA = 0,
     BB = 1,
@@ -63,7 +63,7 @@ Examples:
     FF = 16,
     GG // Problem, forgot to initialize.
   };
-  
+
   unsigned flag = 0;
   flag |= E; // OK.
   flag |=

clang-tools-extra/docs/clang-tidy/checks/bugprone-suspicious-memory-comparison.rst

@@ -16,14 +16,14 @@ properly compare the value representations.
 Objects with the same value may not have the same object representation.
 This may be caused by padding or floating-point types.
 
-See also: 
+See also:
 `EXP42-C. Do not compare padding data
 <https://wiki.sei.cmu.edu/confluence/display/c/EXP42-C.+Do+not+compare+padding+data>`_
 and
 `FLP37-C. Do not use object representations to compare floating-point values
 <https://wiki.sei.cmu.edu/confluence/display/c/FLP37-C.+Do+not+use+object+representations+to+compare+floating-point+values>`_
 
-This check is also related to and partially overlaps the CERT C++ Coding Standard rules 
+This check is also related to and partially overlaps the CERT C++ Coding Standard rules
 `OOP57-CPP. Prefer special member functions and overloaded operators to C Standard Library functions
 <https://wiki.sei.cmu.edu/confluence/display/cplusplus/OOP57-CPP.+Prefer+special+member+functions+and+overloaded+operators+to+C+Standard+Library+functions>`_
 and

clang-tools-extra/docs/clang-tidy/checks/cert-dcl37-c.rst

@@ -6,5 +6,5 @@ cert-dcl37-c
 ============
 
 The cert-dcl37-c check is an alias, please see
-`bugprone-reserved-identifier <bugprone-reserved-identifier.html>`_ for more 
+`bugprone-reserved-identifier <bugprone-reserved-identifier.html>`_ for more
 information.