catch3/include/internal, branch v2.2.3 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. v2.2.3 2018-06-06T21:19:06+00:00 Martin Hořeňovský 2018-06-06T21:16:06+00:00 d2a130f2433aeaca070e3e4d6298a80049d21cfc 






Fix ambiguity in stringification
2018-06-06T20:33:03+00:00

Julien Nitard

2018-05-31T02:32:59+00:00

7be8a41adf368b48350e5906568adf34579d4718

Happening when using clang and templated operators, clang cannot decide
between the operator provided by ReusableStringStream and the one provided
by the value value as both are templates. This is easily solved by calling
the operator<< through the member syntax.

Fixes #1285





Happening when using clang and templated operators, clang cannot decide
between the operator provided by ReusableStringStream and the one provided
by the value value as both are templates. This is easily solved by calling
the operator<< through the member syntax.

Fixes #1285







Finish fixing invalid compilation using MinGW
2018-06-04T21:49:40+00:00

Lyashenko Arsenii Maksimovich

2018-05-01T11:52:24+00:00

021fcee63667e346c619e04bbae932bcea562334












Add missing catch_platform include to compiler capabilities
2018-06-04T21:19:55+00:00

Martin Hořeňovský

2018-06-04T14:53:21+00:00

3a47b8b072d05941a6f0b59b330e98f070519fc0

This was removed in 64be2ad, to fix OS X approval tests. At the time
I couldn't investigate because I didn't have access to OS X, but this
fixed it (and since we don't have MinGW in CI, the breakage went
unnoticed).

As it turns out, piece-wise compilation of the Compact
reporter had broken OS X detection for a long time, and fixing it
was what broke the approvals. After the approval scripts were
changed to compensate, this change passes approval tests and fixes





This was removed in 64be2ad, to fix OS X approval tests. At the time
I couldn't investigate because I didn't have access to OS X, but this
fixed it (and since we don't have MinGW in CI, the breakage went
unnoticed).

As it turns out, piece-wise compilation of the Compact
reporter had broken OS X detection for a long time, and fixing it
was what broke the approvals. After the approval scripts were
changed to compensate, this change passes approval tests and fixes







Ensure stack size for POSIX signal handling is sufficient
2018-05-29T20:29:04+00:00

BiCapitalization

2018-05-27T16:12:40+00:00

88d7b8da25e9975793099bb4003a6f6729913e70

Until now, the stack size for POSIX signal handling was determined by
the implementation defined limit `STKSZ`, which in some cases turned out
to be insufficient, leading to stack overflow inside the signal handler.
The new size, which was determined experimentally, is the larger of 32kb
or `MINSTKSZ`.

Fixes #1225





Until now, the stack size for POSIX signal handling was determined by
the implementation defined limit `STKSZ`, which in some cases turned out
to be insufficient, leading to stack overflow inside the signal handler.
The new size, which was determined experimentally, is the larger of 32kb
or `MINSTKSZ`.

Fixes #1225







Move FALLBACK_STRINGIFIER to before the enum and range fallbacks
2018-05-14T18:38:05+00:00

Martin Hořeňovský

2018-05-14T17:46:30+00:00

4c7b7d04fe304d575b7f683db33eb6a7d11ca888

This should align more closely with the intended semantics, where
types without `StringMaker` specialization or `operator<<` overload
are passed down to the user defined fallback stringifier.

Related to #1024





This should align more closely with the intended semantics, where
types without `StringMaker` specialization or `operator<<` overload
are passed down to the user defined fallback stringifier.

Related to #1024







Add stringification support to std::exception and deriving classes
2018-05-12T15:46:25+00:00

Martin Hořeňovský

2018-05-12T15:46:25+00:00

6c5c4c43a0056b82b2e94b5664c44074348ea8eb

This support is based on overriden `std::exception::what` method, so
if an exception does not do so meaningfully, the message is still
pointless.

This is only used as a fallback, both `StringMaker` specialization and
`operator<<` overload have priority..





This support is based on overriden `std::exception::what` method, so
if an exception does not do so meaningfully, the message is still
pointless.

This is only used as a fallback, both `StringMaker` specialization and
`operator<<` overload have priority..







Provide a polyfill over `std::to_string`
2018-05-09T19:47:42+00:00

Martin Hořeňovský

2018-05-09T18:16:27+00:00

0074926e5cd815f004b4f33961ca89fc5754c8c6

Android apparently does not support `std::to_string`, so we add a
small polyfill over it. Right now only the ULP matcher uses it,
but we have had plans to use it in `StringMaker<int>` and friends,
as it performs a lot better than `std::stringstream` based
stringification on MSVC.

See #1280 for more details





Android apparently does not support `std::to_string`, so we add a
small polyfill over it. Right now only the ULP matcher uses it,
but we have had plans to use it in `StringMaker<int>` and friends,
as it performs a lot better than `std::stringstream` based
stringification on MSVC.

See #1280 for more details







Only use tmpfile workaround for MSVC and not MinGW and friends
2018-04-30T21:19:39+00:00

Martin Hořeňovský

2018-04-30T21:06:26+00:00

ae590fe2163270685ebec4ed1541d3e8e9401692

Fixes #1270





Fixes #1270







Fix missing include and wrong comment format
2018-04-30T13:15:59+00:00

Martin Hořeňovský

2018-04-30T13:15:59+00:00

0510d4755f715d21695ea4a5b15069d69789d7a2

While the comment format was valid C++, it breaks our tooling badly.
I opened up a github issue for our tooling, because unexpected
formatting of a block comment should not silently generate invalid
single header file, see #1269.





While the comment format was valid C++, it breaks our tooling badly.
I opened up a github issue for our tooling, because unexpected
formatting of a block comment should not silently generate invalid
single header file, see #1269.