[Bug libstdc++/44436] New: Associative containers lack emplace() and emplace_hint() methods.

[Bug libstdc++/44436] New: Associative containers lack emplace() and emplace_hint() methods.

[jack2 at cantab dot net]

C++0x associative containers should have emplace() and emplace_hint() methods,
but those in libstdc++ do not.


-- 
           Summary: Associative containers lack emplace() and emplace_hint()
                    methods.
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jack2 at cantab dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436

[Bug libstdc++/44436] Associative containers lack emplace() and emplace_hint() methods.

[paolo dot carlini at oracle dot com]

------- Comment #1 from paolo dot carlini at oracle dot com  2010-06-07 14:03 -------
Yes, we lack *tons* of other C++0x things.


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436

[Bug libstdc++/44436] [C++0x] Implement insert(&&) and emplace* in associative and unordered containers

[paolo dot carlini at oracle dot com]

------- Comment #2 from paolo dot carlini at oracle dot com  2010-06-21 17:47 -------
Reopening


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |
            Summary|Associative containers lack |[C++0x] Implement insert(&&)
                   |emplace() and emplace_hint()|and emplace* in associative
                   |methods.                    |and unordered containers


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436

[Bug libstdc++/44436] [C++0x] Implement insert(&&) and emplace* in associative and unordered containers

[paolo dot carlini at oracle dot com]

------- Comment #3 from paolo dot carlini at oracle dot com  2010-06-21 17:48 -------
I'm working on these, maybe will be ready in time for 4.6.0.


-- 

paolo dot carlini at oracle dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |paolo dot carlini at oracle
                   |dot org                     |dot com
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-06-21 17:48:26
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436

[Bug libstdc++/44436] [C++0x] Implement insert(&&) and emplace* in associative and unordered containers

[redi at gcc dot gnu dot org]

------- Comment #4 from redi at gcc dot gnu dot org  2010-07-08 14:20 -------
*** Bug 44872 has been marked as a duplicate of this bug. ***


-- 

redi at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hyounes at google dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436

[Bug libstdc++/44436] [C++0x] Implement insert(&&) and emplace* in associative and unordered containers

[paolo dot carlini at oracle dot com]

------- Comment #5 from paolo dot carlini at oracle dot com  2010-07-08 14:28 -------
Just to clarify a bit: this wasn't an *oversight*. We had the *nasty* problem
in the Draft C++0x Standard with std::pair, which essentially made impossible
adding the emplace_* members to std::map, std::multimap, etc, without breaking
existing user code. Thus we waited on that, until things got clarified in this
whole area. Now it's actually possible to work on those facilities.

Anyway, much more generally: we are *not* claiming any sort of conformance to
non existing (yet) standards, we are still in experimental mode for C++0x.
Please be patient.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44436