catch3/CMake/CatchMiscFunctions.cmake, branch constexpr_approx Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Allow for `Catch::Approx` to be used in a `constexpr` context 2024-05-18T15:42:42+00:00 Chris Thrasher 2024-05-16T19:23:38+00:00 c974e3097460a8b47d2db00ce4ee9bbb7a19cef9 






Explicitly silence Wnon-virtual-dtor in Decomposer and MatchExpr
2024-04-30T21:51:36+00:00

Martin Hořeňovský

2024-04-30T19:08:35+00:00

fa5a53df17303339eff8fda5cae0b601af207085

Closes #2854





Closes #2854







Add Wsubobject-linkage to warning flags
2024-01-14T20:22:09+00:00

Martin Hořeňovský

2024-01-14T20:22:09+00:00

6ebdd8fac2010a11a85dddbd1a0211c90c8fad96












Fix tests for C++23's multi-arg index operator
2023-10-28T19:49:58+00:00

Martin Hořeňovský

2023-10-28T19:49:49+00:00

79d39a1954837f234b48e3bc342b7f26e535d8a5

Closes #2744





Closes #2744







Fix Wredundant-decls
2023-05-12T07:51:13+00:00

Martin Hořeňovský

2023-05-12T07:50:59+00:00

598895d04866c6e85f1d703a8c3d89e8d38a2311

Closes #2682





Closes #2682







cmake: Improve unreachable-code warnings
2023-04-20T12:53:03+00:00

Holger Kaelberer

2023-04-19T08:12:44+00:00

897fe2a01b7e1983b076ef41f4ce11c5b3e498c6

Enable CI to report -Wunreachable-code-aggressive warnings in clang
builds which covers all,  -Wunreachable-code, -code-break,
-code-return.





Enable CI to report -Wunreachable-code-aggressive warnings in clang
builds which covers all,  -Wunreachable-code, -code-break,
-code-return.







Fix references to license file
2022-10-28T09:30:15+00:00

Lars Toenning

2022-10-28T09:22:53+00:00

f1084fb30990fe40c8f5b70034970c7eb4e1da72

The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1





The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1







CatchMiscFunctions.cmake: Use PRIVATE for target_compile_options (#2553)
2022-10-24T16:26:40+00:00

autoantwort

2022-10-24T16:26:40+00:00

8ce92d2c7288b6b3261caf1c016f8a779b6a8efc

With the changes to how `-ffile-prefix-map` is detected, Catch2 started propagating the flag to its dependents, which isn't the desired behaviour, the normalization should only apply to Catch2's impl.





With the changes to how `-ffile-prefix-map` is detected, Catch2 started propagating the flag to its dependents, which isn't the desired behaviour, the normalization should only apply to Catch2's impl.







improve `-ffile-prefix-map` detection (#2517)
2022-10-04T13:55:50+00:00

Tim Blechmann

2022-10-04T13:55:50+00:00

728de353be6a6d3658932bfc8e1ea5c7742a61c6

the current implementation has two problems:
  * `clang-cl` does not know `-ffile-prefix-map`, but in CMake it is
    reported as "Clang", so the compiler will warn about an unknown
    compiler option.
  * XCode's clang in CMake is reported as "AppleClang", so it is not picked
    up as "Clang", so it is not passed `-ffile-prefix-map`, even though
    it supports it.

Also changed the map so that the normalized `__FILE__` paths are the same
as what the approval tests normalize paths into.

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>




the current implementation has two problems:
  * `clang-cl` does not know `-ffile-prefix-map`, but in CMake it is
    reported as "Clang", so the compiler will warn about an unknown
    compiler option.
  * XCode's clang in CMake is reported as "AppleClang", so it is not picked
    up as "Clang", so it is not passed `-ffile-prefix-map`, even though
    it supports it.

Also changed the map so that the normalized `__FILE__` paths are the same
as what the approval tests normalize paths into.

Co-authored-by: Martin Hořeňovský <martin.horenovsky@gmail.com>






Add Wfloat-equal to default-enabled warnings
2022-05-14T13:47:20+00:00

Martin Hořeňovský

2022-05-14T13:37:39+00:00

fc3d11b1d1090a5bcbcc9e410a460f9bf6a1f474

This is kinda messy, because there is no good way to signal to
the compiler that some code uses direct comparison of floating
point numbers intentionally, so instead we have to use diagnostic
pragmas.

We also have to over-suppress the test files, because Clang (and
possibly GCC) still issue warnings from template instantiation
even if the instantion site is under warning suppression, so the
template definition has to be under warning suppression as well.

Closes #2406





This is kinda messy, because there is no good way to signal to
the compiler that some code uses direct comparison of floating
point numbers intentionally, so instead we have to use diagnostic
pragmas.

We also have to over-suppress the test files, because Clang (and
possibly GCC) still issue warnings from template instantiation
even if the instantion site is under warning suppression, so the
template definition has to be under warning suppression as well.

Closes #2406