[clang-format] [NFC] add recent changes to release notes

[MyDeveloperDay]

Summary

clang-tidy keeps nice release notes of what is added, have clang-format do the same.

[MyDeveloperDay]

@Eugene.Zelenko I've noticed you are always giving excellent review feedback in clang-tidy especially around the documentation, I'd appreciate your eyes on finding the right level of documentation here.

[merge_guards_bot]

Build result: pass - 60143 tests passed, 0 failed and 729 were skipped.
Log files: console-log.txt, CMakeCache.txt

[Eugene.Zelenko]

General comments:

• Isn't Option(s) ... was/were added or Option(s) ... had been added are more correct from from point of view of English grammar? Same for older entries.
• It'll be great to nag developers to expand Release Notes when relevant code changes are made.

clang/docs/ReleaseNotes.rst

322

and between Options and DeriveLineEnding are not necessary.

323

I would suggest to use dot after newlines.

325

UseCRLF should be enclosed in double back-ticks.

328

to insert?

[MyDeveloperDay]

Address review comments
Remove excessive newlines
Remove trailing whitespace

[mitchell-stellar]

LGTM

clang/docs/ReleaseNotes.rst

 
 - -Wtautological-overlap-compare will warn on negative numbers and non-int
   types.
 - -Wtautological-compare for self comparisons and
   -Wtautological-overlap-compare will now look through member and array
   access to determine if two operand expressions are the same.
 - -Wtautological-bitwise-compare is a new warning group.  This group has the
   current warning which diagnoses the tautological comparison of a bitwise
-  operation and a constant.  The group also has the new warning which diagnoses
+  operation and a constant. The group also has the new warning which diagnoses
   when a bitwise-or with a non-negative value is converted to a bool, since
   that bool will always be true.
 - -Wbitwise-conditional-parentheses will warn on operator precedence issues
   when mixing bitwise-and (&) and bitwise-or (|) operator with the
   conditional operator (?:).
 
 Non-comprehensive list of changes in this release
 -------------------------------------------------
- Previous Clang versions contained a work-around to avoid an issue with the
   work-around has now been removed, and users of Visual Studio 2019 are
   encouraged to upgrade to 16.3 or later, otherwise they may see link errors as
   below:
 
   .. code-block:: console
 
     error LNK2005: "bool const std::_Is_integral<int>" (??$_Is_integral@H@std@@3_NB) already defined
 
-
-
-
 C Language Changes in Clang
 ---------------------------
 
 - ...
 
 C11 Feature Support
 ^^^^^^^^^^^^^^^^^^^
 
- The ``Standard`` style option specifies which version of C++ should be used
   when parsing and formatting C++ code. The set of allowed values has changed:
 
   - ``Latest`` will always enable new C++ language features.
   - ``c++03``, ``c++11``, ``c++14``, ``c++17``, ``c++20`` will pin to exactly
     that language version.
   - ``Auto`` is the default and detects style from the code (this is unchanged).
 
   The previous values of ``Cpp03`` and ``Cpp11`` are deprecated. Note that
-  ``Cpp11`` is treated as ``Latest``, as this was always clang-format's behavior.
-  (One motivation for this change is the new name describes the behavior better).
-
-- clang-format gets a new option called ``--dry-run`` or ``-n`` to emit a
-  warning.
+  ``Cpp11`` is treated as ``Latest``, as this was always clang-format's
+  behavior. (One motivation for this change is the new name describes the
+  behavior better).
+
+- Clang-format has a new option called ``--dry-run`` or ``-n`` to emit a
+  warning for clang-format violations. This can be used together
+  with --ferror-limit=N to limit the number of warnings per file and --Werror
+  to make warnings into errors.
 
-- Option *IncludeIsMainSourceRegex* added to allow for additional
+- Option *IncludeIsMainSourceRegex* has been added to allow for additional
   suffixes and file extensions to be considered as a source file
   for execution of logic that looks for "main *include* file" to put
   it on top.
 
   By default, clang-format considers *source* files as "main" only when
   they end with: ``.c``, ``.cc``, ``.cpp``, ``.c++``, ``.cxx``,
   ``.m`` or ``.mm`` extensions. This config option allows to
   extend this set of source files considered as "main".
-            
   For example, if this option is configured to ``(Impl\.hpp)$``,
   then a file ``ClassImpl.hpp`` is considered "main" (in addition to
   ``Class.c``, ``Class.cc``, ``Class.cpp`` and so on) and "main
   include file" logic will be executed (with *IncludeIsMainRegex* setting
   also being respected in later phase). Without this option set,
   ``ClassImpl.hpp`` would not have the main include file put on top
   before any other include.
 
+- Options ``DeriveLineEnding`` and  ``UseCRLF`` have been added to allow
+  clang-format to control the newlines. ``DeriveLineEnding`` is by default
+  ``true`` and reflects is the existing mechanism, which based is on majority
+  rule. The new options allows this to be turned off and ``UseCRLF`` to control
+  the decision as to which sort of line ending to use.
+
+- Option ``SpaceBeforeSquareBrackets`` has been added to insert a space before
+  array declarations.
+
+  .. code-block:: c++
+
+    int a [5];    vs    int a[5];
+
+- Clang-format now supports JavaScript null operators.
+
+  .. code-block:: c++
+
+    const x = foo ?? default;
+    const z = foo?.bar?.baz;
+
 libclang
 --------
 
 - ...
 
-
 Static Analyzer
 ---------------
 
 - The Clang analyzer checker ``DeadStores`` gets a new option called
   ``WarnForDeadNestedAssignments`` to detect nested dead assignments
   (enabled by default).
 - ...
 
.. code-block:: c++
         // ``nullptr``, we must use ``computed`` result.
         if (((base == nullptr) && (computed != nullptr)) ||
             ((base != nullptr) && (computed == nullptr)))
           return computed;
         // Else we can use ``getelementpointer_inbounds()``.
         return getelementpointer_inbounds(base, offset);
       }
 
-
 Core Analysis Improvements
 ==========================
 
 - ...
 
 New Issues Found
 ================