Howard Hinnant 993248935c Accidentally disallowed explicit tuple conversions when all elements of the tuple can be explicitly converted. ... git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@179467 91177308-0d34-0410-b5e6-96231b3b80d8		2013-04-14 00:01:13 +00:00
..
tuple.assign	tuple was accidentally lacking a valid copy assignment operator. It went undetected because I had failed to test assigning from a const lvalue. This fixes http://llvm.org/bugs/show_bug.cgi?id=11921	2012-02-15 20:13:52 +00:00
tuple.cnstr	Accidentally disallowed explicit tuple conversions when all elements of the tuple can be explicitly converted.	2013-04-14 00:01:13 +00:00
tuple.creation	LWG 1385 [FCD] tuple_cat should be a single variadic signature (http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#1385). This issue is only in Ready status, meaning it is not official, but probably will be this March in Madrid. It was tentatively accepted in Batavia with the previso that Bill and I didn't have any problems implementing it. This is my part of that agreement.	2010-12-11 20:47:50 +00:00
tuple.elem	LWG 1191	2010-11-17 19:52:17 +00:00
tuple.helper	LWG 1118	2010-11-17 19:22:43 +00:00
tuple.rel	license change	2010-11-16 22:09:02 +00:00
tuple.special	license change	2010-11-16 22:09:02 +00:00
tuple.swap	license change	2010-11-16 22:09:02 +00:00
tuple.traits	license change	2010-11-16 22:09:02 +00:00
alloc_first.h	Fixing whitespace problems	2010-08-22 00:59:46 +00:00
alloc_last.h	Fixing whitespace problems	2010-08-22 00:59:46 +00:00
allocators.h	Changed __config to react to all of clang's currently documented has_feature flags, and renamed _LIBCPP_MOVE to _LIBCPP_HAS_NO_RVALUE_REFERENCES to be more consistent with the rest of the libc++'s flags, and with clang's nomenclature.	2010-09-04 23:28:19 +00:00
DefaultOnly.h	Fixing whitespace problems	2010-08-22 00:59:46 +00:00
empty_member.pass.cpp	license change	2010-11-16 22:09:02 +00:00
MoveOnly.h	Changed __config to react to all of clang's currently documented has_feature flags, and renamed _LIBCPP_MOVE to _LIBCPP_HAS_NO_RVALUE_REFERENCES to be more consistent with the rest of the libc++'s flags, and with clang's nomenclature.	2010-09-04 23:28:19 +00:00