From 75cc9a102f75cce791021c02d2e3c46cb0b2066b Mon Sep 17 00:00:00 2001 From: Herb Sutter Date: Thu, 28 Jan 2021 11:53:10 -0800 Subject: [PATCH] Improves I.24 rule wording, closes #1733 --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 96c6470..cd9a5e9 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -1232,7 +1232,7 @@ Interface rule summary: * [I.13: Do not pass an array as a single pointer](#Ri-array) * [I.22: Avoid complex initialization of global objects](#Ri-global-init) * [I.23: Keep the number of function arguments low](#Ri-nargs) -* [I.24: Avoid adjacent parameters of the same type when changing the argument order would change meaning](#Ri-unrelated) +* [I.24: Avoid adjacent parameters that can be invoked by the same arguments in either order with different meaning](#Ri-unrelated) * [I.25: Prefer empty abstract classes as interfaces to class hierarchies](#Ri-abstract) * [I.26: If you want a cross-compiler ABI, use a C-style subset](#Ri-abi) * [I.27: For stable library ABI, consider the Pimpl idiom](#Ri-pimpl) @@ -2108,7 +2108,7 @@ There are functions that are best expressed with four individual parameters, but * Warn when a function declares two iterators (including pointers) of the same type instead of a range or a view. * (Not enforceable) This is a philosophical guideline that is infeasible to check directly. -### I.24: Avoid adjacent parameters of the same type when changing the argument order would change meaning +### I.24: Avoid adjacent parameters that can be invoked by the same arguments in either order with different meaning ##### Reason