Skip to content

Commit 0ce8ae3

Browse files
jdennettzygoloid
authored andcommitted
Fix references to container requirements tables.
LWG issue 704 ("MoveAssignable requirement for container value type overly strict") added a reference from [associative.reqmts] to what was at the time table 93 ("Allocator-aware container requirements"). That table is now table 86, but the cross reference is now (incorrectly) to table 83 ("Container requirements"). It should still refer to the Allocator-ware container requirements table. This patch changes it to do so, matching what the committee voted in (many years ago).
1 parent f68ca58 commit 0ce8ae3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

source/containers.tex

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1559,7 +1559,7 @@
15591559
The associative containers meet all the requirements of Allocator-aware
15601560
containers\iref{container.requirements.general}, except that for
15611561
\tcode{map} and \tcode{multimap}, the requirements placed on \tcode{value_type}
1562-
in Table~\ref{tab:containers.container.requirements} apply instead to \tcode{key_type}
1562+
in Table~\ref{tab:containers.allocatoraware} apply instead to \tcode{key_type}
15631563
and \tcode{mapped_type}. \begin{note} For example, in some cases \tcode{key_type} and \tcode{mapped_type}
15641564
are required to be \tcode{CopyAssignable} even though the associated
15651565
\tcode{value_type}, \tcode{pair<const key_type, mapped_type>}, is not
@@ -2176,7 +2176,7 @@
21762176
The unordered associative containers meet all the requirements of Allocator-aware
21772177
containers\iref{container.requirements.general}, except that for
21782178
\tcode{unordered_map} and \tcode{unordered_multimap}, the requirements placed on \tcode{value_type}
2179-
in Table~\ref{tab:containers.container.requirements} apply instead to \tcode{key_type}
2179+
in Table~\ref{tab:containers.allocatoraware} apply instead to \tcode{key_type}
21802180
and \tcode{mapped_type}. \begin{note} For example, \tcode{key_type} and \tcode{mapped_type}
21812181
are sometimes required to be \tcode{CopyAssignable} even though the associated
21822182
\tcode{value_type}, \tcode{pair<const key_type, mapped_type>}, is not

0 commit comments

Comments
 (0)