CWG2758 What is "access and ambiguity control"?

Author: burblebee

source/expressions.tex

@@ -5790,9 +5790,12 @@
 null pointer value
 and the selected deallocation function (see below)
 is not a destroying operator delete,
-the \grammarterm{delete-expression} will invoke the
+evaluating the \grammarterm{delete-expression} invokes the
 destructor (if any) for the object or the elements of the array being
-deleted. In the case of an array, the elements will be destroyed in
+deleted.
+The destructor shall be accessible from the point where
+the \grammarterm{delete-expression} appears.
+In the case of an array, the elements are destroyed in
 order of decreasing address (that is, in reverse order of the completion
 of their constructor; see~\ref{class.base.init}).
 
@@ -5873,8 +5876,7 @@
 \end{note}
 
 \pnum
-If more than one deallocation function is found,
-the function to be called is selected as follows:
+The deallocation the function to be called is selected as follows:
 \begin{itemize}
 \item
 If any of the deallocation functions is a destroying operator delete,
@@ -5903,6 +5905,10 @@
 whether a deallocation function with a parameter of type \tcode{std::size_t}
 is selected.
 \end{itemize}
+Unless the deallocation function is selected
+at the point of definition of the dynamic type's virtual destructor,
+the selected deallocation function shall be accessible
+from the point where the \grammarterm{delete-expression} appears.
 
 \pnum
 For a single-object delete expression,
@@ -5956,10 +5962,6 @@
 the behavior is undefined\iref{new.delete.single,new.delete.array}.
 \end{note}
 
-\pnum
-Access and ambiguity control are done for both the deallocation function
-and the destructor\iref{class.dtor,class.free}.
-
 \rSec2[expr.cast]{Explicit type conversion (cast notation)}%
 \indextext{expression!cast|(}