Author: Nicolas van Kempen Date: 2025-09-08T04:56:10Z New Revision: c5ed3c6073aa6b22baff126b901a297fba7ecf64
URL: https://github.com/llvm/llvm-project/commit/c5ed3c6073aa6b22baff126b901a297fba7ecf64 DIFF: https://github.com/llvm/llvm-project/commit/c5ed3c6073aa6b22baff126b901a297fba7ecf64.diff LOG: [clang-tidy] Minor documentation wording for performance-noexcept-move-constructor (#157384) Fix #157343. Added: Modified: clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst Removed: ################################################################################ diff --git a/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst b/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst index 05f1d85f1af5a..eb605c5b0a53b 100644 --- a/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst +++ b/clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst @@ -9,5 +9,5 @@ marked with ``noexcept`` or marked with ``noexcept(expr)`` where ``expr`` evaluates to ``false`` (but is not a ``false`` literal itself). Move constructors of all the types used with STL containers, for example, -need to be declared ``noexcept``. Otherwise STL will choose copy constructors +should be declared ``noexcept``. Otherwise STL may choose copy constructors instead. The same is valid for move assignment operations. _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
