[clang-tools-extra] [clang-tidy] Add options to throw unannotated functions in `bugprone-exception-escape` (PR #168324)

via cfe-commits cfe-commits at lists.llvm.org
Thu Nov 27 08:22:43 PST 2025


================
@@ -72,14 +72,22 @@ Options
    Comma separated list containing type names which are not counted as thrown
    exceptions in the check. Default value is an empty string.
 
-.. option:: KnownUnannotatedAsThrowing
-
-   When `true`, treat calls to functions with visible definitions that are not
-   explicitly declared as non-throwing (i.e. lack ``noexcept`` or ``throw()``)
-   as potentially throwing, even if their bodies are visible and no explicit
-   throw is found. Default value is `false`.
-
-.. option:: UnknownAsThrowing
-
-   When `true`, treat calls to functions without visible definitions as
-   potentially throwing. Default value is `false`.
+.. option:: TreatFunctionsWithoutSpecificationAsThrowing
+
+   Determines which functions are considered as throwing if they do not have
+   an explicit exception specification. It can be set to the following values:
+
+   ``None``
----------------
zeyi2 wrote:

> Also list syntax should be used. Same below.

Hi Engene, thanks for the review! 

I noticed that `bugprone-signal-handler` and `misc-use-internal-linkage` also use the definition list style with double backticks for their options, which is why I followed that pattern.

It seems there is some inconsistency in the existing documentation:

- https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/docs/clang-tidy/checks/misc/use-internal-linkage.rst?plain=1
- https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/docs/clang-tidy/checks/bugprone/signal-handler.rst?plain=1

I'm happy to update this PR to use standard bullet lists if that is the preferred style now. Should I also open a separate PR to align those other files with this standard?


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


More information about the cfe-commits mailing list