catch3/include, branch v2.11.3 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. v2.11.3 2020-03-19T12:50:19+00:00 Martin Hořeňovský 2020-03-19T12:50:19+00:00 255aa5f2afe1a622c97422f65ace6ca915be0d8d 






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.







v2.11.2
2020-03-19T11:37:51+00:00

Martin Hořeňovský

2020-03-19T11:37:51+00:00

5f94c8dafb56c06892ef37b181df88b46bec0156












Different approach to proper colouring of filters
2020-03-19T10:08:01+00:00

Martin Hořeňovský

2020-02-15T20:18:56+00:00

5561d0342dfbfb6882361aeb519bbdfb49fa6eb8












Switch back to uncolored output after printing filters
2020-03-19T10:08:01+00:00

Till Hofmann

2020-02-10T13:52:35+00:00

3a15315a37c16a5cebee30788a19023f85b9f401

After printing the list of filters, switch back from yellow to black
before printing a newline to avoid the remaining output to be colored in
yellow.





After printing the list of filters, switch back from yellow to black
before printing a newline to avoid the remaining output to be colored in
yellow.







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







Don't cast nanoseconds to integers when writing output
2020-03-08T11:10:44+00:00

khyperia

2020-02-26T14:32:34+00:00

022b61ff9218b427831a182b8df929fde36a20eb












include <iterator> in catch_stats.hpp
2020-02-24T18:36:34+00:00

khyperia

2020-02-24T11:21:32+00:00

87b5bf77bc98030bdbca52bff65ee24fc6483d3b

needed for std::back_inserter on some platforms





needed for std::back_inserter on some platforms







Specialize CATCH_TRAP() for iOS + thumb instruction set combo
2020-02-15T20:45:09+00:00

Martin Hořeňovský

2020-02-15T20:31:31+00:00

81d52c4a5ffc1e527ce158c7570aa94dadc8c002

Fixes #1862





Fixes #1862







Add command line option 'never' to --wait-for-keypress (#1866)
2020-02-15T19:42:57+00:00

Tristan Stenner

2020-02-15T19:42:57+00:00

200b8b6fc05934149d9d4fa56eefbfd613ee73ea

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





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