Howard Hinnant 0527c6207a I believe tuple is still under development in the standard. Daniel Krugler is/will be making convincing arguments that a modified form of LWG 2051 (currently NAD Future) is easily acheivable and desirable. He has demonstrated that a tuple<T...> where all of the T are implicitly convertible from U... should have a tuple constructor that is also implicit, instead of explicit. This would support the use cases in LWG 2051 while not undermining T... with explicit conversions from U.... This check-in is an experimental implementation of Daniel's work. I believe this work to be mature enough to warrant inclusion into libc++. If anyone sees real-world problems that this check in causes, please let me know and I will revert it, and provide the feedback to the LWG. ...

llvm-svn: 153855

2012-04-01 23:10:42 +00:00

..

allocator.adaptor

Test adjustment for recent changes in allocator_traits

2010-12-10 19:22:37 +00:00

date.time

license change

2010-11-16 22:09:02 +00:00

function.objects

Starting using murmur2 when combining multiple size_t's into a single hash, and also for basic_string. Also made hash<thread::id> ever so slighly more portable. I had to tweak one test which is questionable (definitely not portable) anyway.

2011-12-05 00:08:45 +00:00

memory

Modernize relational operators for shared_ptr and unique_ptr. This includes adding support for nullptr, and using less<T*>. Fixes http://llvm.org/bugs/show_bug.cgi?id=12056.

2012-02-21 21:02:58 +00:00

meta

Hook up to the new clang __is_trivially_constructible and __is_trivially_assignable traits. Fixes r10925427 and http://llvm.org/bugs/show_bug.cgi?id=12038.

2012-02-24 23:32:26 +00:00

ratio

Fix ratio arithmetic with zero

2011-11-01 23:13:37 +00:00

template.bitset

Clean up a bunch of warnings in the tests, 3 of which actually turned out to be test bugs.

2011-05-17 19:12:55 +00:00

time

Update testsuite strucuture to latest draft

2010-11-23 19:52:19 +00:00

tuple

I believe tuple is still under development in the standard. Daniel Krugler is/will be making convincing arguments that a modified form of LWG 2051 (currently NAD Future) is easily acheivable and desirable. He has demonstrated that a tuple<T...> where all of the T are implicitly convertible from U... should have a tuple constructor that is also implicit, instead of explicit. This would support the use cases in LWG 2051 while not undermining T... with explicit conversions from U.... This check-in is an experimental implementation of Daniel's work. I believe this work to be mature enough to warrant inclusion into libc++. If anyone sees real-world problems that this check in causes, please let me know and I will revert it, and provide the feedback to the LWG.

2012-04-01 23:10:42 +00:00

type.index

Fixing up some ABI issues

2011-07-07 21:03:52 +00:00

utilities.general

license change

2010-11-16 22:09:02 +00:00

utility

test for pair piecewise construction

2011-06-22 23:51:19 +00:00

utility.requirements

license change

2010-11-16 22:09:02 +00:00

nothing_to_do.pass.cpp

license change

2010-11-16 22:09:02 +00:00