commit | 8b805c915a3847e72b6bb028e9fb3af1b17349df | [log] [tgz] |
---|---|---|
author | Howard Hinnant <[email protected]> | Fri May 25 22:04:21 2012 |
committer | Howard Hinnant <[email protected]> | Fri May 25 22:04:21 2012 |
tree | eca09a65e87c1a27efd6e8acc9ec951dcfe2d3b4 | |
parent | 7b29885463742ee73d2585d9d8fd8926d4222f73 [diff] |
The rules for emplace in map, multimap, unordered_map and unordered_multimap changed a while back and I'm just now updating to these new rules. In a nutshell, you've got to know you're emplacing to a pair and use one of pair's constructors. I made one extension: If you want to emplace the key and default construct the mapped_type, you can just emplace(key), as opposed to emplace(piecewise_construct, forward_as_tuple(key), forward_as_tuple()). llvm-svn: 157503