Merge pull request #2767 from corob-msft/cr-acro-analysis

ttorble · web-flow · commit 032995487367 · 2020-03-29T10:00:08.000+01:00
Acrolinx fixes to C26432
diff --git a/docs/code-quality/c26432.md b/docs/code-quality/c26432.md
@@ -13,7 +13,7 @@ ms.assetid: f587b05a-5c69-4176-baa6-fcb79d228b24
 **C++ Core Guidelines**:
 [C.21: If you define or =delete any default operation, define or =delete them all](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#c21-if-you-define-or-delete-any-default-operation-define-or-delete-them-all)
 
-Special operations like constructors are assumed to alter behavior of types so that they rely more on language mechanisms to automatically enforce specific scenarios (the canonical example is resource management). If any of these operations is explicitly defined, defaulted or deleted (as an indication that user wants to avoid any special handling of a type) it would be inconsistent to leave the other operations from the same group unspecified (i.e. implicitly defined by compiler).
+Special operations like constructors are assumed to alter behavior of types so that they rely more on language mechanisms to automatically enforce specific scenarios. The canonical example is resource management. If you explicitly define, default, or delete any of these special operations, it signals you want to avoid any special handling of a type. It's inconsistent to leave the other operations unspecified, that is, implicitly defined as deleted by the compiler.
 
 ## Remarks
 
@@ -22,7 +22,7 @@ Special operations like constructors are assumed to alter behavior of types so t
   - move constructors;
   - copy assignment operators;
   - move assignment operators;
-  - destructors;
-- The rule doesn't check if operations are defined in the same way, i.e. it is okay to mix deleted and defaulted operations with explicitly defined, but they all must be specified somehow if any of them appears.
-- Access levels are not important and can also be mixed.
+  - destructors.
+- The rule doesn't check if operations are defined in the same way. It's okay to mix deleted and defaulted operations with explicitly defined ones. However, you must specify all of them if you specify any of them.
+- Access levels aren't important and can also be mixed.
 - The warning flags the first non-static function definition of a type, once per type.
