Howard Hinnant 635ce1d127 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()). ... git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@157503 91177308-0d34-0410-b5e6-96231b3b80d8		2012-05-25 22:04:21 +00:00
..
map	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()).	2012-05-25 22:04:21 +00:00
multimap	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()).	2012-05-25 22:04:21 +00:00
multiset	Fixed PR10574: http://llvm.org/bugs/show_bug.cgi?id=10574	2011-08-12 21:56:02 +00:00
set	Fixed PR10574: http://llvm.org/bugs/show_bug.cgi?id=10574	2011-08-12 21:56:02 +00:00
tree_balance_after_insert.pass.cpp	license change	2010-11-16 22:09:02 +00:00
tree_left_rotate.pass.cpp	license change	2010-11-16 22:09:02 +00:00
tree_remove.pass.cpp	license change	2010-11-16 22:09:02 +00:00
tree_right_rotate.pass.cpp	license change	2010-11-16 22:09:02 +00:00