[special] Clarify that we are using overload resolution to determine the

corresponding constructor, not performing overload resolution "on" it (whatever that might mean). Editorially fixes CWG 2197.
cplusplus · Nov 12, 2016 · 6953b24 · 6953b24
1 parent 829560f
commit 6953b24
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/source/special.tex b/source/special.tex
@@ -201,7 +201,7 @@
 with a \grammarterm{brace-or-equal-initializer}, has
 class type \tcode{M} (or array thereof) and either \tcode{M}
 has no default constructor or overload resolution
-(\ref{over.match}) as applied to \tcode{M}'s default
+(\ref{over.match}) as applied to find \tcode{M}'s corresponding
 constructor results in an ambiguity or in a function that is deleted or
 inaccessible from the defaulted default constructor, or
 
@@ -2641,7 +2641,7 @@
 
 \item a potentially constructed subobject type
   \tcode{M} (or array thereof) that cannot be copied/moved because
-  overload resolution (\ref{over.match}), as applied to
+  overload resolution (\ref{over.match}), as applied to find
   \tcode{M}'s 
   corresponding constructor, results in an ambiguity or 
   a function that is deleted or inaccessible from the
@@ -2944,7 +2944,7 @@
 \item a direct non-static data member of class type \tcode{M}
   (or array thereof) or a direct base class \tcode{M}
   that cannot be copied/moved because overload resolution
-  (\ref{over.match}), as applied to \tcode{M}'s corresponding
+  (\ref{over.match}), as applied to find \tcode{M}'s corresponding
   assignment operator, results in an ambiguity or
   a function that is deleted or inaccessible from the
   defaulted assignment operator.