| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
the unnecessary ones, and commented the ones that are there for non-obvious reasons such as to help things limp along in C++03 language mode.
llvm-svn: 189039
|
|
|
|
| |
llvm-svn: 188320
|
|
|
|
|
|
| |
explained in <http://lists.cs.uiuc.edu/pipermail/cfe-dev/2013-August/031214.html>.
llvm-svn: 188192
|
|
|
|
|
|
| |
[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
|
|
|
|
|
|
| |
two flags: _LIBCPP_TYPE_VIS and _LIBCPP_FUNC_VIS. This is in preparation for taking advantage of clang's new __type_visibility__ attribute.
llvm-svn: 176593
|
|
|
|
|
|
| |
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: 146345
|
|
|
|
| |
llvm-svn: 145410
|
|
|
|
| |
llvm-svn: 142235
|
|
|
|
| |
llvm-svn: 137522
|
|
|
|
|
|
| |
http://llvm.org/bugs/show_bug.cgi?id=10191
llvm-svn: 134248
|
|
|
|
| |
llvm-svn: 134190
|
|
|
|
|
|
| |
that is reverted. Recently clang appears to have tightened up its definition of is_convertible and that has caused some failures in [unordered_][multi]map. I've switched to using is_constructible to restablish the desired functionality in [unordered_][multi]map. Specifically, inserting rvalues of move-only types for the keys.
llvm-svn: 133402
|
|
|
|
|
|
| |
The purpose is to aid automated documentation tools.
llvm-svn: 133008
|
|
|
|
| |
llvm-svn: 132640
|
|
|
|
| |
llvm-svn: 132639
|
|
|
|
| |
llvm-svn: 129266
|
|
|
|
|
|
| |
consistent with gcc. Opened an LWG issue on this one. 2) Renamed some private typedefs which are causing boost grief.
llvm-svn: 126576
|
|
|
|
|
|
| |
qualified (thanks Chris).
llvm-svn: 125510
|
|
|
|
| |
llvm-svn: 124726
|
|
|
|
| |
llvm-svn: 122825
|
|
|
|
| |
llvm-svn: 119395
|
|
|
|
| |
llvm-svn: 114551
|
|
|
|
| |
llvm-svn: 113089
|
|
|
|
|
|
| |
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: 111750
|
|
|
|
| |
llvm-svn: 110828
|
|
|
|
| |
llvm-svn: 103516
|
|
llvm-svn: 103490
|