llvm-project.git/libcxx/test/std/containers/sequences/array/empty.verify.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [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++] Remove unnecessary main() function in .compile.pass.cpp and .verify.cpp tests 2023-03-17T21:56:21+00:00 Louis Dionne ldionne.2@gmail.com 2023-03-16T16:45:41+00:00 72f0edf3f4291d2614719a8c8af21a7a62ed5d74 We pretty consistently don't define those cause they are not needed, and it removes the potential pitfall to think that these tests are being run. This doesn't touch .compile.fail.cpp tests since those should be replaced by .verify.cpp tests anyway, and there would be a lot to fix up. As a fly-by, I also fixed a bit of formatting, removed a few unused includes and made some very minor, clearly NFC refactorings such as in allocator.traits/allocator.traits.members/allocate.verify.cpp where the old test basically made no sense the way it was written. Differential Revision: https://reviews.llvm.org/D146236 
We pretty consistently don't define those cause they are not needed,
and it removes the potential pitfall to think that these tests are
being run. This doesn't touch .compile.fail.cpp tests since those
should be replaced by .verify.cpp tests anyway, and there would be
a lot to fix up.

As a fly-by, I also fixed a bit of formatting, removed a few unused
includes and made some very minor, clearly NFC refactorings such as
in allocator.traits/allocator.traits.members/allocate.verify.cpp where
the old test basically made no sense the way it was written.

Differential Revision: https://reviews.llvm.org/D146236
[libc++] Remove "// -*- C++ -*-" comments from all .cpp files. NFCI. 2021-10-01T16:06:59+00:00 Arthur O'Dwyer arthur.j.odwyer@gmail.com 2021-09-30T19:43:38+00:00 d4b59a05fc7507cf69993109443dc5af47ae4fa8 Even if these comments have a benefit in .h files (for editors that care about language but can't be configured to treat .h as C++ code), they certainly have no benefit for files with the .cpp extension. Discussed in D110794. 
Even if these comments have a benefit in .h files (for editors that
care about language but can't be configured to treat .h as C++ code),
they certainly have no benefit for files with the .cpp extension.

Discussed in D110794.
[libc++] Remove the c++98 Lit feature from the test suite 2020-06-03T13:37:22+00:00 Louis Dionne ldionne@apple.com 2020-06-01T14:38:23+00:00 31cbe0f240f660f15602c96b787c58a26f17e179 C++98 and C++03 are effectively aliases as far as Clang is concerned. As such, allowing both std=c++98 and std=c++03 as Lit parameters is just slightly confusing, but provides no value. It's similar to allowing both std=c++17 and std=c++1z, which we don't do. This was discovered because we had an internal bot that ran the test suite under both c++98 AND c++03 -- one of which is redundant. Differential Revision: https://reviews.llvm.org/D80926 
C++98 and C++03 are effectively aliases as far as Clang is concerned.
As such, allowing both std=c++98 and std=c++03 as Lit parameters is
just slightly confusing, but provides no value. It's similar to allowing
both std=c++17 and std=c++1z, which we don't do.

This was discovered because we had an internal bot that ran the test
suite under both c++98 AND c++03 -- one of which is redundant.

Differential Revision: https://reviews.llvm.org/D80926
[libc++] Make the verify-support feature implicit 2020-04-30T15:47:12+00:00 Louis Dionne ldionne@apple.com 2020-04-27T16:49:01+00:00 2fd7d364cd999c743b5bdefa7ee9e5630f3564ad Tests that require support for Clang-verify are already marked as such explicitly by their extension, which is .verify.cpp. Requiring the use of an explicit Lit feature is, after thought, not really helpful. This is a change in design: we have been bitten in the past by tests not being enabled when we thought they were. However, the issue was mostly with file extensions being ignored. The fix for that is not to blindly require explicit features all the time, but instead to report all files that are in the suite but that don't match any known test format. This can be implemented in a follow-up patch. 
Tests that require support for Clang-verify are already marked as such
explicitly by their extension, which is .verify.cpp. Requiring the use
of an explicit Lit feature is, after thought, not really helpful.

This is a change in design: we have been bitten in the past by tests not
being enabled when we thought they were. However, the issue was mostly
with file extensions being ignored. The fix for that is not to blindly
require explicit features all the time, but instead to report all files
that are in the suite but that don't match any known test format. This
can be implemented in a follow-up patch.
[libc++] Move .fail.cpp tests with verify-support to .verify.cpp 2020-04-17T13:05:28+00:00 Louis Dionne ldionne@apple.com 2020-04-17T12:47:40+00:00 9a39d5a2ecf7c9290d334f2697c3a4e533aa4bea