Howard Hinnant de589f2f8f Peter Collingbourne: If a pointer is passed as the third argument of the (iterator, ... iterator, allocator) constructor with the intention of it being implicitly converted to the allocator type, it is possible for overload resolution to favour the (iterator, iterator, enable_if) constructor. Eliminate this possibility by moving the enable_if to one of the existing arguments and removing the third argument. git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@191145 91177308-0d34-0410-b5e6-96231b3b80d8		2013-09-21 21:13:54 +00:00
..
array	N3644 tests for map/multimap/set/multiset. Drive-by NOEXCEPT for __tree_const_iterator constructor. Fix comment typos in other tests	2013-08-08 21:52:50 +00:00
deque	LWG Issue 2210 (Part #1): deque	2013-09-07 16:16:19 +00:00
dynarray	Initial implementation of <dynarray>. No allocator support pending resolution of LWG #2235; no stack allocation pending compiler support	2013-09-13 15:22:55 +00:00
forwardlist	A collection of minor type-o fixes. The first two aren't testable, but all tests pass with them. I stumbled across them while experimenting with a std::move that checks its argument for non-const. The third corrects a test that is currently failing.	2013-09-12 00:10:44 +00:00
list	Remove a tab that snuck in	2013-09-08 21:13:57 +00:00
vector	Peter Collingbourne: If a pointer is passed as the third argument of the (iterator,	2013-09-21 21:13:54 +00:00
vector.bool	LWG Issue 2210 (Part #7): vector and vector<bool>	2013-09-14 00:47:59 +00:00
nothing_to_do.pass.cpp	license change	2010-11-16 22:09:02 +00:00