Changes in array

4887d047 - [libc++][NFC] Replace enable_if with __enable_if_t in a few places

Sun, 03 Jul 2022 23:21:44 +0000

[libc++][NFC] Replace enable_if with __enable_if_t in a few placesReviewed By: ldionne, #libcSpies: jloser, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D128400 List of files: /llvm-project-15.0.7/libcxx/include/array

de4a57cb - [libc++] Re-add transitive includes that had been removed since LLVM 14

Mon, 27 Jun 2022 19:53:41 +0000

[libc++] Re-add transitive includes that had been removed since LLVM 14This commit re-adds transitive includes that had been removed by4cd04d1687f1, c36870c8e79c, a83f4b9cda57, 1458458b558d, 2e2f3158c604,and 489637e66dd3. This should cover almost all the includes that hadbeen removed since LLVM 14 and that would contribute to breaking usercode when releasing LLVM 15.It is possible to disable the inclusion of these headers by defining_LIBCPP_REMOVE_TRANSITIVE_INCLUDES. The intent is that vendors willenable that macro and start fixing downstream issues immediately. Wecan then remove the macro (and the transitive includes) by default ina future release. That way, we will break users only once by removingtransitive includes in bulk instead of doing it bit by bit a everyrelease, which is more disruptive for users.Note 1: The set of headers to re-add was found by re-generating the transitive include test on a checkout of release/14.x, which provided the list of all transitive includes we used to provide.Note 2: Several includes of , , and have been added in this commit. These transitive inclusions were added when we implemented boyer_moore_searcher in .Note 3: This is a best effort patch to try and resolve downstream breakage caused since branching LLVM 14. I wasn't able to perfectly mirror transitive includes in LLVM 14 for a few headers, so I added a release note explaining it. To summarize, adding boyer_moore_searcher created a bunch of circular dependencies, so we have to break backwards compatibility in a few cases.Differential Revision: https://reviews.llvm.org/D128661 List of files: /llvm-project-15.0.7/libcxx/include/array

db1978b6 - [libc++] Mark standard-mandated includes as such

Thu, 16 Jun 2022 20:43:46 +0000

[libc++] Mark standard-mandated includes as suchReviewed By: ldionne, Mordante, #libc, saugustineSpies: saugustine, MaskRay, arichardson, mstorsjo, jloser, libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D127953 List of files: /llvm-project-15.0.7/libcxx/include/array

4cd04d16 - [libc++] Removes unneeded includes.

Mon, 13 Jun 2022 18:05:36 +0000

[libc++] Removes unneeded includes.Reviewed By: #libc, philnikDifferential Revision: https://reviews.llvm.org/D127675 List of files: /llvm-project-15.0.7/libcxx/include/array

3cd4531b - [libc++] Granularize includes

Fri, 10 Jun 2022 17:53:10 +0000

[libc++] Granularize includesReviewed By: ldionne, #libcSpies: libcxx-commits, wenleiDifferential Revision: https://reviews.llvm.org/D127445 List of files: /llvm-project-15.0.7/libcxx/include/array

385cc25a - [libc++] Ensure that all public C++ headers include <__assert>

Fri, 25 Mar 2022 16:55:36 +0000

[libc++] Ensure that all public C++ headers include <__assert>This patch changes the requirement for getting the declaration of theassertion handler from including <__assert> to including any publicC++ header of the library. Note that C compatibility headers areexcluded because we don't implement all the C headers ourselves --some of them are taken straight from the C library, like assert.h.It also adds a generated test to check it. Furthermore, this newgenerated test is designed in a way that will make it possible toreplace almost all the existing test-generation scripts with thissystem in upcoming patches.Differential Revision: https://reviews.llvm.org/D122506 List of files: /llvm-project-15.0.7/libcxx/include/array

1458458b - [libc++] Remove includes

Mon, 07 Mar 2022 15:31:33 +0000

[libc++] Remove includesReviewed By: ldionne, Quuxplusone, #libcSpies: libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D121054 List of files: /llvm-project-15.0.7/libcxx/include/array

52915d78 - [libc++] Granularize includes

Sat, 05 Mar 2022 18:17:07 +0000

[libc++] Granularize includesReviewed By: ldionne, #libcSpies: EricWF, libcxx-commits, arphamanDifferential Revision: https://reviews.llvm.org/D120466 List of files: /llvm-project-15.0.7/libcxx/include/array

f87aa19b - [libc++] Move everything related solely to _LIBCPP_ASSERT to its own file

Mon, 14 Feb 2022 18:41:09 +0000

[libc++] Move everything related solely to _LIBCPP_ASSERT to its own fileThis is the first step towards disentangling the debug mode and assertionsin libc++. This patch doesn't make any functional change: it simply moves_LIBCPP_ASSERT-related stuff to its own file so as to make it clear thatlibc++ assertions and the debug mode are different things. Future patcheswill make it possible to enable assertions without enabling the debugmode.Differential Revision: https://reviews.llvm.org/D119769 List of files: /llvm-project-15.0.7/libcxx/include/array

2e2f3158 - [libc++] Granularize algorithm includes

Tue, 15 Feb 2022 17:18:08 +0000

[libc++] Granularize algorithm includesReviewed By: Mordante, ldionne, Quuxplusone, #libc, #libc_abiSpies: #libc_vendors, libcxx-commits, miyukiDifferential Revision: https://reviews.llvm.org/D119667 List of files: /llvm-project-15.0.7/libcxx/include/array

2a8f9a5e - [libc++] Implement P0627R6 (Function to mark unreachable code)

Mon, 14 Feb 2022 17:26:02 +0000

[libc++] Implement P0627R6 (Function to mark unreachable code)Reviewed By: ldionne, Quuxplusone, #libcSpies: arichardson, mstorsjo, libcxx-commits, mgornyDifferential Revision: https://reviews.llvm.org/D119152 List of files: /llvm-project-15.0.7/libcxx/include/array

fa6b9e40 - [libc++] Normalize all our '#pragma GCC system_header', and regression-test.

Wed, 02 Feb 2022 01:16:40 +0000

[libc++] Normalize all our '#pragma GCC system_header', and regression-test.Now we'll notice if a header forgets to include this magic phrase.Differential Revision: https://reviews.llvm.org/D118800 List of files: /llvm-project-15.0.7/libcxx/include/array

eb8650a7 - [runtimes][NFC] Remove filenames at the top of the license notice

Wed, 17 Nov 2021 21:25:01 +0000

[runtimes][NFC] Remove filenames at the top of the license noticeWe've stopped doing it in libc++ for a while now because these nameswould end up rotting as we move things around and copy/paste stuff.This cleans up all the existing files so as to stop the spreadingas people copy-paste headers around. List of files: /llvm-project-15.0.7/libcxx/include/array

4e0ea2cf - [libc++] Use enable_if_t instead of _EnableIf

Tue, 17 Aug 2021 16:26:09 +0000

[libc++] Use enable_if_t instead of _EnableIfI just ran into a compiler error involving __bind_back and some overloadsthat were being disabled with _EnableIf. I noticed that the error messagewas quite bad and did not mention the reason for the overload beingexcluded. Specifically, the error looked like this: candidate template ignored: substitution failure [with _Args = ]: no member named '_EnableIfImpl' in 'std::_MetaBase'Instead, when using enable_if or enable_if_t, the compiler is clever andcan produce better diagnostics, like so: candidate template ignored: requirement 'is_invocable_v< std::__bind_back_op<1, std::integer_sequence>, std::ranges::views::__transform::__fn &, std::tuple &, ContiguousView>' was not satisfied [with _Args = ]Basically, it tries to do a poor man's implementation of concepts, whichis already a lot better than simply complaining about substitution failure.Hence, this commit uses enable_if_t instead of _EnableIf wheneverpossible. That is both more straightforward than using the internalhelper, and also leads to better error messages in those cases.I understand the motivation for _EnableIf's implementation was to improvecompile-time performance, however I believe striving to improve errormessages is even more important for our QOI, hence this patch. Furthermore,it is unclear that _EnableIf actually improved compile-time performancein any noticeable way (see discussion in the review for details).Differential Revision: https://reviews.llvm.org/D108216 List of files: /llvm-project-15.0.7/libcxx/include/array

01666904 - [libc++] Remove workarounds for the lack of deduction guides in C++17

Tue, 17 Aug 2021 15:59:07 +0000

[libc++] Remove workarounds for the lack of deduction guides in C++17All supported compilers have supported deduction guides in C++17 for awhile, so this isn't necessary anymore.Differential Revision: https://reviews.llvm.org/D108213 List of files: /llvm-project-15.0.7/libcxx/include/array

bfbd73f8 - [libc++] Alphabetize and include-what-you-use. NFCI.

Wed, 19 May 2021 15:57:04 +0000

[libc++] Alphabetize and include-what-you-use. NFCI.Differential Revision: https://reviews.llvm.org/D102781 List of files: /llvm-project-15.0.7/libcxx/include/array

4cd6ca10 - [libc++] NFC: Normalize `#endif //` comment indentation

Tue, 20 Apr 2021 16:03:32 +0000

[libc++] NFC: Normalize `#endif //` comment indentation List of files: /llvm-project-15.0.7/libcxx/include/array

781c476c - [libc++] ADL-proof vector by adding _VSTD:: qualification on calls.

Wed, 16 Dec 2020 00:32:29 +0000

[libc++] ADL-proof vector by adding _VSTD:: qualification on calls.This affects only vectors with weird/malicious allocators,the same corner case covered in D91708, but for `vector` this time.Also ADL-proof <__tree>, which affects only sets and maps with weird/maliciousallocators where the ADL trap is in the *fancy pointer type*.Also drive-by _VSTD:: qualification in the guts of std::bind,std::packaged_task, std::condition_variable.Differential Revision: https://reviews.llvm.org/D93424 List of files: /llvm-project-15.0.7/libcxx/include/array

d586f92c - [libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.

Fri, 27 Nov 2020 16:02:06 +0000

[libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.I used a lot of `git grep` to find places where `std::` was being usedoutside of comments and assert-messages. There were three outcomes:- Qualified function calls, e.g. `std::move` becomes `_VSTD::move`. This is the most common case.- Typenames that don't need qualification, e.g. `std::allocator` becomes `allocator`. Leaving these as `_VSTD::allocator` would also be fine, but I decided that removing the qualification is more consistent with existing practice.- Names that specifically need un-versioned `std::` qualification, or that I wasn't sure about. For example, I didn't touch any code in , , , or any ext/ or experimental/ headers; and I didn't touch any instances of `std::type_info`.In some deduction guides, we were accidentally using `class Alloc = typename std::allocator`,despite `std::allocator`'s type-ness not being template-dependent.Because `std::allocator` is a qualified name, this did parse as we intended;but what we meant was simply `class Alloc = allocator`.Differential Revision: https://reviews.llvm.org/D92250 List of files: /llvm-project-15.0.7/libcxx/include/array

12805513 - [libc++] Remove some workarounds for C++03

Fri, 09 Oct 2020 16:33:49 +0000

[libc++] Remove some workarounds for C++03We don't support any compiler that doesn't support variadics and rvaluereferences in C++03 mode, so these workarounds can be dropped. There'sstill *a lot* of cruft related to these workarounds, but I try to tacklea bit of it here and there. List of files: /llvm-project-15.0.7/libcxx/include/array