llvm-project.git/libcxx/test/std/containers/sequences/array/array.cons/initialization.pass.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [libcxx][test] Fix typos (#155217) 2025-08-25T10:02:51+00:00 Stephan T. Lavavej stl@nuwen.net 2025-08-25T10:02:51+00:00 abf91449a3d4896d11aa7bea3a9acede614ce778 I noticed a typo in the directory name `refwrap.comparissons`, then did a quick pass to fix typos elsewhere in the tests. All fixes were manual (some carefully search-and-replaced); I used [cspell](https://www.npmjs.com/package/cspell) to find them. 
I noticed a typo in the directory name `refwrap.comparissons`, then did
a quick pass to fix typos elsewhere in the tests.

All fixes were manual (some carefully search-and-replaced); I used
[cspell](https://www.npmjs.com/package/cspell) to find them.
 [libc++][NFC] Run the container tests through clang-format (#126499) 2025-02-11T05:17:39+00:00 Louis Dionne ldionne.2@gmail.com 2025-02-11T05:17:39+00:00 2d66ab5e8ede4f893b272f5ad1231e87504d7235 We've been improving these the tests for vector quite a bit and we are probably not done improving our container tests. Formatting everything at once will make subsequent reviews easier. 
We've been improving these the tests for vector quite a bit and we are
probably not done improving our container tests. Formatting everything
at once will make subsequent reviews easier.
 [libc++][test] Fix MSVC warning C4127 in `array.cons/initialization.pass.cpp` (#79793) 2024-03-09T10:31:58+00:00 Stephan T. Lavavej stl@nuwen.net 2024-03-09T10:31:58+00:00 1c7607e8ee6ec4ca3abce1561dd39a98d4efac96 This fixes MSVC warning C4127: conditional expression is constant. Testing `TEST_STD_AT_LEAST_20_OR_RUNTIME_EVALUATED` by itself doesn't emit this warning, but the condition here is more complicated. I'm expanding the macro and mechanically simplifying the resulting code. (Yeah, this warning is often annoying, and I introduced `TEST_STD_AT_LEAST_20_OR_RUNTIME_EVALUATED` to avoid this warning elsewhere, so it's disappointing that it doesn't make the compiler happy here. If this change is undesirable, I can replace it with `ADDITIONAL_COMPILE_FLAGS(cl-style-warnings)`, but ideally I'd like to avoid having to suppress it.) --------- Co-authored-by: Louis Dionne <ldionne.2@gmail.com> 
This fixes MSVC warning C4127: conditional expression is constant.

Testing `TEST_STD_AT_LEAST_20_OR_RUNTIME_EVALUATED` by itself doesn't
emit this warning, but the condition here is more complicated. I'm
expanding the macro and mechanically simplifying the resulting code.

(Yeah, this warning is often annoying, and I introduced
`TEST_STD_AT_LEAST_20_OR_RUNTIME_EVALUATED` to avoid this warning
elsewhere, so it's disappointing that it doesn't make the compiler happy
here. If this change is undesirable, I can replace it with
`ADDITIONAL_COMPILE_FLAGS(cl-style-warnings)`, but ideally I'd like to
avoid having to suppress it.)

---------

Co-authored-by: Louis Dionne <ldionne.2@gmail.com>
 [libc++] Fix constexpr initialization of std::array<T, 0> (#74667) 2023-12-15T21:06:12+00:00 Louis Dionne ldionne.2@gmail.com 2023-12-15T21:06:12+00:00 70bcd81e7a7365d2fa98a2d08ba81305eb7846f1 This patch fixes constexpr default initialization of empty arrays and improves the tests accordingly. Fixes #74375 
This patch fixes constexpr default initialization of empty arrays and
improves the tests accordingly.

Fixes #74375
 [libc++] Fix issues with the triviality of std::array 2020-05-29T23:32:55+00:00 Louis Dionne ldionne@apple.com 2020-05-29T23:32:55+00:00 7265ff928a974a844b6301c139cbb0f957532da9 The Standard is currently unimplementable. We have to pick between: 1. Not implementing constexpr support properly in std::array<T, 0> 2. Making std::array<T, 0> non-trivial even when T is trivial 3. Returning nullptr from std::array<T, 0>::begin() Libc++ initially picked (1). In 77b9abfc8e89, we started implementing constexpr properly, but lost the guarantee of triviality. Since it seems like both (1) and (2) are really important, it seems like (3) is the only viable option for libc++, after all. This is also what other implementations are doing. This patch moves libc++ from (1) to (3). It also: - Improves the test coverage for the various ways of initializing std::array - Adds tests for the triviality of std::array - Adds tests for the aggregate-ness of std::array Reviewed By: #libc, miscco, EricWF, zoecarver Differential Revision: https://reviews.llvm.org/D80821 
The Standard is currently unimplementable. We have to pick between:

1. Not implementing constexpr support properly in std::array<T, 0>
2. Making std::array<T, 0> non-trivial even when T is trivial
3. Returning nullptr from std::array<T, 0>::begin()

Libc++ initially picked (1). In 77b9abfc8e89, we started implementing constexpr properly, but lost the guarantee of triviality. Since it seems like both (1) and (2) are really important, it seems like (3) is the only viable option for libc++, after all. This is also what other implementations are doing.

This patch moves libc++ from (1) to (3).

It also:
- Improves the test coverage for the various ways of initializing std::array
- Adds tests for the triviality of std::array
- Adds tests for the aggregate-ness of std::array

Reviewed By: #libc, miscco, EricWF, zoecarver

Differential Revision: https://reviews.llvm.org/D80821