catch3/include/internal, branch v2.13.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. v2.13.2 2020-10-07T09:43:02+00:00 Martin Hořeňovský 2020-10-07T09:43:02+00:00 87074da73ecb1c2e7c35fd14f50ca21c4c002adc 






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







Workaround AppleClang bug by renaming TestHasher constructor argument
2020-10-02T21:22:49+00:00

Martin Hořeňovský

2020-10-02T21:22:49+00:00

7c75ecaef441e951a1b9240c5400e2947f190d48

As far as I understand the standard, if there is a function called
`rng` in the global namespace, and a function argument called `rng`,
then the argument should shadow the function. This then means that
uses of `rng` inside the function should refer to the argument.

This is not the case for AppleClang 12.0.0. Luckily the workaround
is simple enough; just rename the argument. Given that the function
is 3 lines and uncomplicated, the change of the name doesn't really
affect readability.

Still, WTF AppleClang?

Closes #2030





As far as I understand the standard, if there is a function called
`rng` in the global namespace, and a function argument called `rng`,
then the argument should shadow the function. This then means that
uses of `rng` inside the function should refer to the argument.

This is not the case for AppleClang 12.0.0. Luckily the workaround
is simple enough; just rename the argument. Given that the function
is 3 lines and uncomplicated, the change of the name doesn't really
affect readability.

Still, WTF AppleClang?

Closes #2030







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












Make experimental capture work on Windows with read-write temp file behavior
2020-09-10T18:14:18+00:00

Travis Wilson

2020-09-01T00:19:56+00:00

a2e5ce241839c55a85e52ea12d7b444f2cbe20e0












v2.13.1
2020-09-07T10:34:55+00:00

Martin Hořeňovský

2020-09-07T10:34:55+00:00

fd9f5ac661f87335ecd70d39849c1d3a90f1c64d












Remove superfluous values
2020-08-27T09:15:58+00:00

Dawid Kurek

2020-08-24T08:03:04+00:00

f0dc4d9be078d21ccabcb0798f03c332a153f84f

The `0`s were needed for the expansion of parameter pack for the sake of
expander. Now when we have `index++` it is no more needed.





The `0`s were needed for the expansion of parameter pack for the sake of
expander. Now when we have `index++` it is no more needed.







Support sentinel-based ranges in default stringify (#2004)
2020-08-18T08:34:47+00:00

Sean Middleditch

2020-08-18T08:34:47+00:00

284672cc84f3fd53332618d1654d95bc4254ff3f












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.







v2.13.0
2020-07-12T18:28:38+00:00

Martin Hořeňovský

2020-07-12T18:28:38+00:00

7f21cc6c5599f59835f769debf13b4c3e6148a28