catch3/src/catch2/internal, branch v3.0.0-preview3 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Improve detection of std::uncaught_exceptions support 2020-10-08T10:39:50+00:00 Martin Hořeňovský 2020-10-06T09:07:53+00:00 3f9e779542eac5576b54987614b77a1260ecdbac 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-08T09:41:05+00:00 Martin Hořeňovský 2020-10-02T21:22:49+00:00 b601b7facadf8053d36b548d19d91a6cfe90acbd 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-10-08T09:34:57+00:00 Will Pazner 2020-09-17T16:45:43+00:00 a4dfcf9042ffa066739b67a44c4b15e6fb45affd 






Make experimental capture work on Windows with read-write temp file behavior
2020-10-08T09:28:50+00:00

Travis Wilson

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

b0214ff862508ca77ce76b9028aaf8422d7083b9












Remove superfluous whitespace before #include
2020-09-07T18:01:04+00:00

Martin Hořeňovský

2020-09-07T18:01:04+00:00

99d70c0c9dbbea98bcbb9f34e2576ebb34ddd046












Remove superfluous values
2020-09-07T12:30:58+00:00

Dawid Kurek

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

8f44e09a7257425946fafb5fa0dd70114a2d2f07

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.







Issue 1992: Better c++17 std::byte detection
2020-09-07T11:01:51+00:00

Gregory Bond

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

5ad1a4fe6138272db57c4f8e98931be77e4c3c5b

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.







console colour: fix unintended colouring of user's stderr on POSIX
2020-09-07T09:53:45+00:00

Martin Jeřábek

2020-09-04T10:27:16+00:00

8851e779cf43e206c8eeb24229e26d8f6608e3cf

At some places, the colour reset code is printed after a newline.
Since the default output buffering to console is line-based, the reset
code is not actually written out. If messages from user code are printed
to stderr (different stream, same console), they are printed before
the colour reset code, and thus they are coloured.

Explicitly flushing the stream after writing the colour escape code solves
this.





At some places, the colour reset code is printed after a newline.
Since the default output buffering to console is line-based, the reset
code is not actually written out. If messages from user code are printed
to stderr (different stream, same console), they are printed before
the colour reset code, and thus they are coloured.

Explicitly flushing the stream after writing the colour escape code solves
this.







Sweep out Wshadow
2020-09-06T11:11:42+00:00

Martin Hořeňovský

2020-09-06T11:10:43+00:00

cc18bd719da38e5415909f5b10199395f00076e6

Most of the changes are completely pointless renaming of constructor
arguments so that they do not use the same name as the type members,
but :shrug:

Closes #2015





Most of the changes are completely pointless renaming of constructor
arguments so that they do not use the same name as the type members,
but :shrug:

Closes #2015







Add standardized copyright notice + SPDX identifier to source files
2020-08-30T13:43:45+00:00

Martin Hořeňovský

2020-08-30T13:43:45+00:00

90aeffb97d6942d16f75a56b11e10fc0b010995a

This should also be done for test files, but that has lower priority.





This should also be done for test files, but that has lower priority.