Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[associative.reqmts.general],[unord.req.general] Fix cross-references to [container.alloc.reqmts] and [container.reqmts] #7249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jensmaurer merged 1 commit into from
Sep 8, 2024
Merged

[associative.reqmts.general],[unord.req.general] Fix cross-references to [container.alloc.reqmts] and [container.reqmts] #7249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/containers.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2726,12 +2726,12 @@
\pnum
A type \tcode{X} meets the \defnadj{associative}{container} requirements
if \tcode{X} meets all the requirements of an allocator-aware
container\iref{container.reqmts} and
container\iref{container.alloc.reqmts} and
the following types, statements, and expressions are well-formed and
have the specified semantics,
except that for
\tcode{map} and \tcode{multimap}, the requirements placed on \tcode{value_type}
in \ref{container.alloc.reqmts} apply instead to \tcode{key_type}
in \ref{container.reqmts} apply instead to \tcode{key_type}
and \tcode{mapped_type}.
\begin{note}
For example, in some cases \tcode{key_type} and \tcode{mapped_type}
Expand Down Expand Up @@ -4225,11 +4225,11 @@
A type \tcode{X} meets
the \defnadj{unordered associative}{container} requirements
if \tcode{X} meets all the requirements of
an allocator-aware container\iref{container.reqmts} and
an allocator-aware container\iref{container.alloc.reqmts} and
the following types, statements, and expressions are well-formed and
have the specified semantics,
except that for \tcode{unordered_map} and \tcode{unordered_multimap},
the requirements placed on \tcode{value_type} in \ref{container.alloc.reqmts}
the requirements placed on \tcode{value_type} in \ref{container.reqmts}
apply instead to \tcode{key_type} and \tcode{mapped_type}.
\begin{note}
For example, \tcode{key_type} and \tcode{mapped_type}
Expand Down