catch3/include/internal/catch_compiler_capabilities.h, branch v2.13.6 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Add lcc to the list of unwanted compilers that mimic gcc 2021-04-04T12:05:39+00:00 Pavel Kamenov 2021-03-30T06:25:38+00:00 4cb3220a8a648eb5af5c250c939ed49c648cfc04 






Improve detection of std::uncaught_exceptions support
2020-10-06T09:07:53+00:00

Martin Hořeňovský

2020-10-06T09:07:53+00:00

e6f5e05ebcc46355fe737d8d747f8ed95edc99d1

The problem was that Catch2 did not reliably include `<exception>`
before it checked for the feature test macro for
`std::uncaught_exceptions`. To avoid overhead of including
`<exception>` everywhere, the configuration check was split out
into a separate header.

Closes #2021





The problem was that Catch2 did not reliably include `<exception>`
before it checked for the feature test macro for
`std::uncaught_exceptions`. To avoid overhead of including
`<exception>` everywhere, the configuration check was split out
into a separate header.

Closes #2021







Disable __builtin_constant_p when compiling with nvcc
2020-09-18T14:07:18+00:00

Will Pazner

2020-09-17T16:45:43+00:00

00db4fb4970a3f31900581b8018dd77cdbc8f2b4












Issue 1992: Better c++17 std::byte detection
2020-08-03T12:38:56+00:00

Gregory Bond

2020-08-03T03:03:19+00:00

708487d201dad267a7846596f5830286dec2cde0

This fixed buld errors for ubuntu-16 + clang and similar situations
where C++17 is supported in the compiler but not the default
C++ standard library.





This fixed buld errors for ubuntu-16 + clang and similar situations
where C++17 is supported in the compiler but not the default
C++ standard library.







Silence clang-tidy's hicpp-vararg (alias of coreguidelines vararg)
2020-05-09T16:23:12+00:00

Martin Hořeňovský

2020-05-09T16:23:09+00:00

f0e596e2522f64451f6444edab5c59b8b9e8e082

Ideally, clang-tidy would be smart that if one alias of a warning
is suppressed, then the other one is suppressed as well, but as of
right now, it isn't. This means that for now we have to suppress
both aliases of this warning. Opened upstream issue to fix this:
https://bugs.llvm.org/show_bug.cgi?id=45859

Obviously, ideally clang-tidy would also not warn that we are calling
a vararg function when it is an unevaluated magic builtin, but that
also is not happening right now and I opened an issue for it:
https://bugs.llvm.org/show_bug.cgi?id=45860

Closes #1921





Ideally, clang-tidy would be smart that if one alias of a warning
is suppressed, then the other one is suppressed as well, but as of
right now, it isn't. This means that for now we have to suppress
both aliases of this warning. Opened upstream issue to fix this:
https://bugs.llvm.org/show_bug.cgi?id=45859

Obviously, ideally clang-tidy would also not warn that we are calling
a vararg function when it is an unevaluated magic builtin, but that
also is not happening right now and I opened an issue for it:
https://bugs.llvm.org/show_bug.cgi?id=45860

Closes #1921







Use macro to determine whether std::uncaught_exceptions is available
2020-04-14T21:03:58+00:00

John Else

2020-04-13T15:10:36+00:00

6fbe5efc717a72c9749c5590c96524e92cddeca6

Catch assumes std::uncaught_exceptions is available whenever C++17 is
available, but for macOS versions older than 10.12 this is not the case.

Instead of checking the C++ version, use a macro to check whether the
feature is available.





Catch assumes std::uncaught_exceptions is available whenever C++17 is
available, but for macOS versions older than 10.12 this is not the case.

Instead of checking the C++ version, use a macro to check whether the
feature is available.







Remove usage of __builtin_constant_p under IBM XL
2020-04-10T18:55:23+00:00

Andrew Gaspar

2020-04-09T23:52:33+00:00

035a0625964a2db0252719904f581d1072d691a1












Suppress clang-tidy warning about vararg usage in assertion macros
2020-04-02T18:45:57+00:00

Moritz Haase

2020-04-02T12:22:01+00:00

d399a308d04b885433396f4198c0cda999f28d77

CATCH_INTERNAL_IGNORE_BUT_WARN() introduced with b7b346c triggers
clang-tidy warning 'cppcoreguidelines-pro-type-vararg' for every usage
of assertion macros like CHECK() and REQUIRE(). Silence it via NOLINT
in the '#if defined(__clang__)' block only, as clang-tidy honors those.





CATCH_INTERNAL_IGNORE_BUT_WARN() introduced with b7b346c triggers
clang-tidy warning 'cppcoreguidelines-pro-type-vararg' for every usage
of assertion macros like CHECK() and REQUIRE(). Silence it via NOLINT
in the '#if defined(__clang__)' block only, as clang-tidy honors those.







Fix compilation error when lambdas are used in assertions
2020-03-19T12:32:45+00:00

Martin Hořeňovský

2020-03-19T12:32:45+00:00

3a33315ff8e047b1ff46b1ee2a5be3fdd7fbac08

This is a partial revert of b7b346c3e5603.





This is a partial revert of b7b346c3e5603.







Make warnings in assertions fire for GCC/Clang again
2020-03-19T08:45:41+00:00

Martin Hořeňovský

2020-03-18T19:59:25+00:00

b7b346c3e56030d19ac58d33326b69bbaf226552

The old code caused warnings to fire under MSVC, and Clang <3.8.
I could not find a GCC version where it worked, but I assume that it
did at some point.

This new code causes all of MSVC, GCC, Clang, in current versions,
to emit signed/unsigned comparison warning in test like this:

```cpp
TEST_CASE() {
    int32_t i = -1;
    uint32_t j = 1;
    REQUIRE(i != j);
}
```

Where previously only MSVC would emit the warning.

Fixes #1880





The old code caused warnings to fire under MSVC, and Clang <3.8.
I could not find a GCC version where it worked, but I assume that it
did at some point.

This new code causes all of MSVC, GCC, Clang, in current versions,
to emit signed/unsigned comparison warning in test like this:

```cpp
TEST_CASE() {
    int32_t i = -1;
    uint32_t j = 1;
    REQUIRE(i != j);
}
```

Where previously only MSVC would emit the warning.

Fixes #1880