catch3/include/internal/benchmark/detail, branch v2.13.0 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Really fix use of std::result_of when invoke_result is available 2020-05-22T08:05:34+00:00 Martin Hořeňovský 2020-05-21T19:39:19+00:00 77dc8cfc45e7bae1d1219bac2e06bac87eb8c6b1 Closes #1934 
Closes #1934
Avoid using std::result_of when std::invoke_result is available 2020-05-21T19:39:19+00:00 Martin Hořeňovský 2020-05-21T19:39:19+00:00 ddc9f4c61df438952a4c0c2e451d25677ecf4b2b Closes #1934 
Closes #1934
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
Added <random> include for std::uniform_int_distribution 2020-01-14T11:48:09+00:00 Matthias Moulin 2020-01-14T11:48:09+00:00 4ea74ff9662177987606791b0a0391210b214848 






Rework how warning suppression in macros is done
2019-10-27T20:07:21+00:00

Martin Hořeňovský

2019-10-27T20:07:21+00:00

849f2848bdf625a7b6248e4e62ba0e39ee609634

Previously, each warning suppression was self-contained, with its
own pair of `SUPPRESS_X_WARNING` and `UNSUPPRESS_X_WARNING` macros.
This had the obvious advantage of being self-containing, but it
also meant that if we needed to suppress more than one warning
in a single place, then we would manipulate the compiler's warning
state multiple times, even though logically we would only need one
layer.

The new way of suppressing warnings in macros is to push compiler's
warning state with `CATCH_INTERNAL_START_WARNINGS_SUPPRESSION` macro,
then disable whatever macros we need with the
`CATCH_INTERNAL_SUPPRESS_X_WARNINGS` macro, and then return to the
previous state using `CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION`.





Previously, each warning suppression was self-contained, with its
own pair of `SUPPRESS_X_WARNING` and `UNSUPPRESS_X_WARNING` macros.
This had the obvious advantage of being self-containing, but it
also meant that if we needed to suppress more than one warning
in a single place, then we would manipulate the compiler's warning
state multiple times, even though logically we would only need one
layer.

The new way of suppressing warnings in macros is to push compiler's
warning state with `CATCH_INTERNAL_START_WARNINGS_SUPPRESSION` macro,
then disable whatever macros we need with the
`CATCH_INTERNAL_SUPPRESS_X_WARNINGS` macro, and then return to the
previous state using `CATCH_INTERNAL_STOP_WARNINGS_SUPPRESSION`.







Standardize and document the parallel processing toggle
2019-06-15T10:50:36+00:00

Martin Hořeňovský

2019-06-15T10:50:36+00:00

c365ac392b3b4edf1cb232407111902146249404












Move the async-using parts of benchmarking into a .cpp file
2019-06-15T09:43:25+00:00

Martin Hořeňovský

2019-06-15T09:14:24+00:00

e640c3837aaf3d627f8f77998cf3cd142ee139fa

This keeps it out of the main include path when benchmarking is
enabled, somewhat reducing the compilation-time penalty.

Also moved some other functions into the .cpp file, especially
helpers that could be given internal linkage, and concretized some
iterator-templated code that only ever used
`std::vector<double>::iterator`.





This keeps it out of the main include path when benchmarking is
enabled, somewhat reducing the compilation-time penalty.

Also moved some other functions into the .cpp file, especially
helpers that could be given internal linkage, and concretized some
iterator-templated code that only ever used
`std::vector<double>::iterator`.







Integrate Nonius benchmark into Catch2
2019-06-06T17:33:37+00:00

Joachim Meyer

2019-04-23T21:41:13+00:00

ce2560ca956c1743f8bc871e0bf95f65a3db887c

Changes done to Nonius:
* Moved things into "Catch::Benchmark" namespace
* Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros
* Removed Nonius's parameters for benchmarks, Generators should be used instead
* Added relevant methods to the reporter interface (default-implemented, to avoid
breaking existing 3rd party reporters)
* Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default
on MSVC
* Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of
benchmarking from Catch





Changes done to Nonius:
* Moved things into "Catch::Benchmark" namespace
* Benchmarks were integrated with `TEST_CASE`/`SECTION`/`GENERATE` macros
* Removed Nonius's parameters for benchmarks, Generators should be used instead
* Added relevant methods to the reporter interface (default-implemented, to avoid
breaking existing 3rd party reporters)
* Async processing is guarded with `_REENTRANT` macro for GCC/Clang, used by default
on MSVC
* Added a macro `CATCH_CONFIG_DISABLE_BENCHMARKING` that removes all traces of
benchmarking from Catch