- da0a0e8 Make tuple's constructor and std::get<>(tuple) constexpr. Final stage of fixing bug #16599. Thanks to Howard for the review and updates. by Marshall Clow · 11 years ago
- 8fc4f5a Make std::get constexpr by Marshall Clow · 11 years ago
- 01a0e90 Make std::forward and std::move (and std::move_if_noexcept) constexpr in C++14 by Marshall Clow · 11 years ago
- e8029e5 Implement n3584 - Addressing Tuples by Type by Marshall Clow · 11 years ago
- 9932489 Accidentally disallowed explicit tuple conversions when all elements of the tuple can be explicitly converted. by Howard Hinnant · 11 years ago
- 83eade6 No functionality change at this time. I've split _LIBCPP_VISIBLE up into two flags: _LIBCPP_TYPE_VIS and _LIBCPP_FUNC_VIS. This is in preparation for taking advantage of clang's new __type_visibility__ attribute. by Howard Hinnant · 12 years ago
- 9c0df14 Rename uses of _ and __ because these are getting stepped on by macros from other system code. by Howard Hinnant · 12 years ago
- 33be35e Dimitry Andric: many visibility fixes. Howard: Much appreciated. Can you send me a patch to CREDITS.TXT? by Howard Hinnant · 12 years ago
- 46e9493 Appy constexpr to <memory>. Picked up a few missing noexcepts as well. by Howard Hinnant · 12 years ago
- 74f26f2 Apply noexcept to tuple. by Howard Hinnant · 12 years ago
- 4eebfc3 As a conforming extension give tuple a noexcept default constructor conditionalized on its held types. by Howard Hinnant · 12 years ago
- 5394c1e Give tuple a constexpr default constructor. by Howard Hinnant · 12 years ago
- dc1345f 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. by Howard Hinnant · 12 years ago
- 2848444 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 by Howard Hinnant · 13 years ago
- 6cc99fa Fix http://llvm.org/bugs/show_bug.cgi?id=11616 by Howard Hinnant · 13 years ago
- d4cf215 Fix http://llvm.org/bugs/show_bug.cgi?id=11461. Credit Alberto Ganesh Barbati. by Howard Hinnant · 13 years ago
- ec3773c Quash a whole bunch of warnings by Howard Hinnant · 13 years ago
- 9996844 Further macro protection by replacing _[A-Z] with _[A-Z]p by Howard Hinnant · 13 years ago
- 08e1747 Windows support by Ruben Van Boxem. by Howard Hinnant · 13 years ago
- 15e48f9 Fix <rdar://problem/10226704> by Howard Hinnant · 13 years ago
- 0949eed _STD -> _VSTD to avoid macro clash on windows by Howard Hinnant · 13 years ago
- aabf287 Experimental support for a meaningful __is_swappable<T>::value. This does not appear to be strictly needed for correct functioning of the library. If it causes any problems, I'd rather pull it sooner rather than later. by Howard Hinnant · 13 years ago
- a5e0121 noexcept for <tuple>. And in the process learned that I had done it wrong for pair's swap. I needed to create an __is_nothrow_swappable<T>::value trait that was smart enought to answer false when __is_swappable<T>::value is false. Otherwise one gets compile-time errors when using pair or tuple of non-swappable types, even if you never try to swap the pair or tuple. by Howard Hinnant · 13 years ago
- 56a85ca tweak for readability (no functionality change) by Howard Hinnant · 14 years ago
- 6c66994 An rvalue reference cannot bind to an lvalue, so static_cast the by Douglas Gregor · 14 years ago
- f83417b Chandler Carruth changed >> to > > in several places. by Howard Hinnant · 14 years ago
- e48e366 Reduced copying cost of tuple_cat from quadratic to linear. by Howard Hinnant · 14 years ago
- 0e1493e 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. by Howard Hinnant · 14 years ago
- cd2254b LWG 1191 by Howard Hinnant · 14 years ago
- 86ed8ae LWG 1118 by Howard Hinnant · 14 years ago
- e049cc5 Cleaning up some tuple code. by Howard Hinnant · 14 years ago
- ee6ccd0 visibility-decoration sweep completed. by Howard Hinnant · 14 years ago
- 324bb03 Fixing whitespace problems by Howard Hinnant · 14 years ago
- e3263b4 GB 85, GB 87 by Howard Hinnant · 14 years ago
- 3c1ffba US 98, US 99 by Howard Hinnant · 14 years ago
- f5256e1 Wiped out some non-ascii characters that snuck into the copyright. by Howard Hinnant · 14 years ago
- bc8d3f9 libcxx initial import by Howard Hinnant · 14 years ago