[lib] Fix cross-references to replaced table cpp17.allocator

Author: jensmaurer

source/iostreams.tex

@@ -12151,8 +12151,8 @@
 \end{codeblock}
 
 \pnum
-\tcode{Allocator} shall meet the \oldconcept{Allocator} requirements
-(\tref{cpp17.allocator}).
+\tcode{Allocator} shall meet
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \pnum
 \begin{example}
@@ -12458,8 +12458,8 @@
 \end{note}
 
 \pnum
-Template parameters named \tcode{Allocator} shall meet the
-\oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+Template parameters named \tcode{Allocator} shall meet
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \rSec2[fs.filesystem.syn]{Header \tcode{<filesystem>} synopsis}
 

source/lib-intro.tex

@@ -2621,8 +2621,7 @@
 \pnum
 \begin{example}
 The following is an allocator class template supporting the minimal
-interface that meets the requirements of
-\tref{cpp17.allocator}:
+interface that meets the requirements of \ref{allocator.requirements.general}:
 
 \begin{codeblock}
 template<class Tp>

source/memory.tex

@@ -815,7 +815,7 @@
 disambiguate constructor and function overloading. Specifically, several types (see
 \tcode{tuple}~\ref{tuple}) have constructors with \tcode{allocator_arg_t} as the first
 argument, immediately followed by an argument of a type that meets the
-\oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+\oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \rSec2[allocator.uses]{\tcode{uses_allocator}}
 
@@ -1913,7 +1913,7 @@
 
 \pnum
 \begin{example}
-Given an allocator type \tcode{X} (\tref{cpp17.allocator}) and
+Given an allocator type \tcode{X}\iref{allocator.requirements.general} and
 letting \tcode{A} be a synonym for \tcode{allocator_traits<X>}, the types \tcode{A::pointer},
 \tcode{A::const_pointer}, \tcode{A::void_pointer}, and \tcode{A::const_void_pointer}
 may be used as \tcode{unique_ptr<T, D>::pointer}.
@@ -3188,7 +3188,8 @@
 initialized with \tcode{std::move(d)} do not throw exceptions.
 The expression \tcode{d(p)}
 has well-defined behavior and does not throw exceptions.
-\tcode{A} meets the \oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+\tcode{A} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \pnum
 \effects
@@ -3673,7 +3674,8 @@
 \begin{itemdescr}
 \pnum
 \expects
-\tcode{A} meets the \oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+\tcode{A} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \pnum
 \effects
@@ -5389,8 +5391,8 @@
 \rSec3[mem.poly.allocator.class.general]{General}
 
 \pnum
-A specialization of class template \tcode{pmr::polymorphic_allocator}
-meets the \oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+A specialization of class template \tcode{pmr::polymorphic_allocator} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 Constructed with different memory resources,
 different instances of the same specialization of \tcode{pmr::polymorphic_allocator}
 can exhibit entirely different allocation behavior.

source/threads.tex

@@ -10137,8 +10137,8 @@
 \begin{itemdescr}
 \pnum
 \expects
-\tcode{Alloc} meets the \oldconcept{Allocator}
-requirements (\tref{cpp17.allocator}).
+\tcode{Alloc} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 \end{itemdescr}
 
 \indexlibraryctor{promise}%

source/utilities.tex

@@ -1861,8 +1861,8 @@
 \begin{itemdescr}
 \pnum
 \expects
-\tcode{Alloc} meets the
-\oldconcept{Allocator} requirements (\tref{cpp17.allocator}).
+\tcode{Alloc} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \pnum
 \effects
@@ -2675,8 +2675,8 @@
 \begin{itemdescr}
 \pnum
 \expects
-\tcode{Alloc} meets the \oldconcept{Allocator}
-requirements (\tref{cpp17.allocator}).
+\tcode{Alloc} meets
+the \oldconcept{Allocator} requirements\iref{allocator.requirements.general}.
 
 \pnum
 \begin{note}