[clang-tools-extra] [clang-tidy][NFC] Fix formatting issue in `clang-tidy` documentations (PR #168722)

via cfe-commits cfe-commits at lists.llvm.org
Sun Dec 14 21:01:05 PST 2025


================
@@ -96,21 +96,22 @@ to be checked. The format is the following, without newlines:
 The functions are matched using POSIX extended regular expressions.
 *(Note: The regular expressions do not support negative* ``(?!)`` *matches.)*
 
-The ``reason`` is optional and is used to provide additional information about the
-reasoning behind the replacement. The default reason is ``is marked as unsafe``.
+The `reason` is optional and is used to provide additional information about
+the reasoning behind the replacement. The default reason is
+`is marked as unsafe`.
 
-If ``replacement`` is empty, the default text ``it should not be used`` will be
+If `replacement` is empty, the default text `it should not be used` will be
 shown instead of the suggestion for a replacement.
 
-If the ``reason`` starts with the character ``>``, the reason becomes fully custom.
-The default suffix is disabled even if a ``replacement`` is present, and only the
-reason message is shown after the matched function, to allow better control over
-the suggestions. (The starting ``>`` and whitespace directly after it are
-trimmed from the message.)
+If the `reason` starts with the character ``>``, the reason becomes fully
----------------
EugeneZelenko wrote:

```suggestion
If the `reason` starts with the character `>`, the reason becomes fully
```

Option value.

https://github.com/llvm/llvm-project/pull/168722


More information about the cfe-commits mailing list