Martin Hořeňovský 849f2848bd Rework how warning suppression in macros is done ... 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`.		2019-10-27 21:07:21 +01:00
..
catch_analyse.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_benchmark_function.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_complete_invoke.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_estimate_clock.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_measure.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_repeat.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_run_for_at_least.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00
catch_stats.cpp	Rework how warning suppression in macros is done	2019-10-27 21:07:21 +01:00
catch_stats.hpp	Move the async-using parts of benchmarking into a .cpp file	2019-06-15 11:43:25 +02:00
catch_timing.hpp	Integrate Nonius benchmark into Catch2	2019-06-06 19:33:37 +02:00