| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
llvm-svn: 224658
|
| |
|
|
| |
llvm-svn: 220154
|
| |
|
|
|
|
| |
count(). Thanks to Jim Porter for the bug report
llvm-svn: 216353
|
| |
|
|
|
|
| |
in 32-bit mode because they assumed that std::size_type and make_unsigned<ptrdiff_t>::type were always the same type. No change to libc++, just the tests.
llvm-svn: 212538
|
| |
|
|
|
|
| |
containers. Still no changes to libc++
llvm-svn: 203480
|
| |
|
|
|
|
| |
explicit. Note that libc++ already did this for string/deque/forward_list/list/vector and the unordered containers; implement it for set/multiset/map/multimap. Add tests for all the containers. Two drive-by fixes as well: add a missing explicit in <deque>, and remove a tab that snuck into a container test. This issue is also LLVM bug 15724, and resolves it.
llvm-svn: 202994
|
| |
|
|
|
|
| |
in C++03
llvm-svn: 201021
|
| |
|
|
|
|
| |
test suite. Moved one to /support, made it a superset, and removed all but one of the others, and iupdated all the includes. Left the odd one (thread/futures/test_allocator.h) for later.
llvm-svn: 196174
|
| |
|
|
|
|
| |
Moved one to /support, removed the other, and iupdated all the includes. No functionality change
llvm-svn: 196118
|
| |
|
|
|
|
| |
/support and delete the other. Then adjust all the tests that used them to include the moved one. No functionality change.
llvm-svn: 195785
|
| |
|
|
|
|
| |
associative and unordered containers. I beleive lack of support for this was accidentally recently introduced (by me) and this is fixing a regression. This time tests are put in to prevent such a regression in the future.
llvm-svn: 191692
|
| |
|
|
|
|
| |
set/multiset. THIS is map/multimap
llvm-svn: 190474
|
| |
|
|
| |
llvm-svn: 190454
|
| |
|
|
| |
llvm-svn: 188320
|
| |
|
|
| |
llvm-svn: 188241
|
| |
|
|
|
|
| |
__tree_const_iterator constructor. Fix comment typos in other tests
llvm-svn: 188019
|
| |
|
|
|
|
| |
[unordered_][multi]map. This fixes http://llvm.org/bugs/show_bug.cgi?id=16549
llvm-svn: 185711
|
| |
|
|
|
|
| |
using just an argument for the key, as opposed to using piecewise_construct. However a bug report exposed that this created an unfortunate ambiguity. People who are currently using the extension will be notified the next time they compile, and will have to change to using piecewise_construct. There are no ABI issues with the removal of this extension. This fixes http://llvm.org/bugs/show_bug.cgi?id=16542
llvm-svn: 185666
|
| |
|
|
|
|
| |
http://llvm.org/bugs/show_bug.cgi?id=16538
llvm-svn: 185665
|
| |
|
|
|
|
| |
for the associative containers only. This work still needs to be done on the unordered and sequence containers. Fixes http://llvm.org/bugs/show_bug.cgi?id=15978
llvm-svn: 184358
|
| |
|
|
|
|
| |
-I to that directory; rename 'iterators.h' to 'iterator_test.h'; remove hard-coded paths to include files from more than 350 source files
llvm-svn: 171594
|
| |
|
|
| |
llvm-svn: 171452
|
| |
|
|
|
|
| |
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
|
| |
|
|
| |
llvm-svn: 137522
|
| |
|
|
| |
llvm-svn: 132640
|
| |
|
|
| |
llvm-svn: 132639
|
| |
|
|
| |
llvm-svn: 128807
|
| |
|
|
| |
llvm-svn: 128797
|
| |
|
|
| |
llvm-svn: 124508
|
| |
|
|
| |
llvm-svn: 119395
|
| |
|
|
|
|
| |
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.
llvm-svn: 113086
|
| |
|
|
| |
llvm-svn: 111755
|
| |
|
|
| |
llvm-svn: 103516
|
|
|
llvm-svn: 103490
|
