catch3/include/internal/benchmark, branch v2.12.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. 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
Make CATCH_BREAK_INTO_DEBUGGER be user-configurable 2020-02-01T16:01:50+00:00 khyperia 2020-01-27T14:43:27+00:00 ccb1f70629e8952c4b92d77535f79ad6c7055d23 






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












Provide const overload of ObjectStorage::stored_object()
2019-12-23T20:22:32+00:00

Martin Hořeňovský

2019-12-23T20:22:32+00:00

e4004e0adb77d897fa4b1446a7f3d3c6bce2016f

Fixes #1820





Fixes #1820







Fix wrong namespacing of benchmarking constructor helpers
2019-11-21T15:22:04+00:00

Joe Burzinski

2019-11-19T04:22:38+00:00

cfba9dce97e8b15f84d4ff329cc065abccf1cea1












Ensure the full benchmarking support is present in the single header
2019-11-15T10:59:43+00:00

Martin Hořeňovský

2019-11-15T10:54:38+00:00

f23f96883a59979e693852ffa9f180eccdd09862

Fixes #1800





Fixes #1800







Fix error when period of steady_clock is not nano
2019-11-01T20:52:38+00:00

cericks0n

2019-11-01T20:52:38+00:00

fa6d52e2a344bb7be7ab03b38ffb3c193be3a84e

On systems where std::chrono::steady_clock::period is not std::nano, benchmark tests fail to compile due to trying to convert analysis.samples from a vector of duration<double, clock::period> to a vector of std::chrono::duration<double, std::nano>.




On systems where std::chrono::steady_clock::period is not std::nano, benchmark tests fail to compile due to trying to convert analysis.samples from a vector of duration<double, clock::period> to a vector of std::chrono::duration<double, std::nano>.






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`.