[clang-tidy] Minor documentation wording for performance-noexcept-move-constructor

[nicovank]

Fix #157343.

[llvmbot]

@llvm/pr-subscribers-clang-tools-extra

Author: Nicolas van Kempen (nicovank)

Changes

Fix #157343.

---

Full diff: https://github.com/llvm/llvm-project/pull/157384.diff

1 Files Affected:

• (modified) clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst (+1-1)

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.

[llvmbot]

@llvm/pr-subscribers-clang-tidy

Author: Nicolas van Kempen (nicovank)

Changes

Fix #157343.

---

Full diff: https://github.com/llvm/llvm-project/pull/157384.diff

1 Files Affected:

• (modified) clang-tools-extra/docs/clang-tidy/checks/performance/noexcept-move-constructor.rst (+1-1)

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.

[nicovank]

Feel free to ship immediately if OK.

Turns out, I can enable and test out auto-merge 😮 let's see what happens.

[nicovank]

Wow, I thought auto merge would wait for a reviewer approval. Oops. Good thing this is harmless. Please let me know if there was an issue.