This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
pair
, not tuple
Section: 23.4 [associative] Status: Resolved Submitter: Paolo Carlini Opened: 2010-10-29 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [associative].
View all issues with Resolved status.
Discussion:
I'm seeing something strange in the paragraphs 23.4.3.4 [map.modifiers] and 23.4.4.3 [multimap.modifiers]:
they both talk about tuple<const key_type, mapped_type>
but I think they
should be talking about pair<const key_type, mapped_type>
because, among
other reasons, a tuple
is not convertible to a pair
. If I replace tuple
with pair
everything makes sense to me.
[ 2010-11-07 Daniel comments ]
This is by far not the only necessary fix within both sub-clauses. For details see the 2010-10-29 comment in 2005(i).
[2011-03-24 Madrid meeting]
Paolo: Don't think we can do it now.
Daniel K: Agrees.[ 2011 Bloomington ]
Consensus that this issue will be resolved by 2005(i), but held open until that issue is resolved.
Proposed resolution:
Apply the resolution proposed by the 2010-10-29 comment in 2005(i).