catch3/src/catch2/benchmark, branch v3.15.0 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Cleanups from static analysis 2026-04-24T09:21:04+00:00 Martin Hořeňovský 2026-04-24T09:21:04+00:00 11a96e186af8b2779d93e550217e9c95d3f89371 






Mark some extra classes final
2026-04-06T22:13:17+00:00

Martin Hořeňovský

2026-04-06T22:13:17+00:00

548e14a8c8147c5d20898d9d97809887ab89ad60












Do not include chrono_clock.hpp in benchmark_stats_fwd.hpp
2026-04-05T12:57:05+00:00

Martin Hořeňovský

2026-04-04T21:25:29+00:00

465e63dad7733f8e014dc043069b1dc64e7c5e75












chore: fix some typos in comments (#3048)
2026-01-03T15:05:18+00:00

bigmoonbit

2026-01-03T15:05:18+00:00

cd4fc88e2a50b59b117a974e69366232243d4f56

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




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






Fix bad error reporting for nested exceptions in default configuration
2025-07-27T19:41:02+00:00

Martin Hořeňovský

2025-07-27T18:28:51+00:00

d547cae549f484dda3c6a2b3cc5f71b9db40e842

Bad handling of `TestFailureException` when translating unexpected
exceptions inside assertion macros led to the unexpected exceptions
handling erroring out through throwing the same exception again.

This was then backstopped by the machinery for handling uncaught
exceptions from assertions, which is normally used by the
`CATCH_CONFIG_FAST_COMPILE` machinery, where we assume that it can
only be invoked because the assertion macros are not configured to
catch assertions.

Closes #1292





Bad handling of `TestFailureException` when translating unexpected
exceptions inside assertion macros led to the unexpected exceptions
handling erroring out through throwing the same exception again.

This was then backstopped by the machinery for handling uncaught
exceptions from assertions, which is normally used by the
`CATCH_CONFIG_FAST_COMPILE` machinery, where we assume that it can
only be invoked because the assertion macros are not configured to
catch assertions.

Closes #1292







Use variable templates
2025-04-28T03:14:04+00:00

ZXShady

2025-04-27T18:55:56+00:00

4ff57aba42938478f8b626c0862409f6eb7548f0












Remove unused headers
2025-04-27T17:08:41+00:00

Chris Thrasher

2025-04-26T16:08:05+00:00

5a6d70eebbf8201c7c76ea26fb1bb06cceeee5c3












Explicitly cast values of different types
2024-10-14T19:37:35+00:00

Sven Fischer

2024-05-23T14:49:57+00:00

0b2af562710d1bac7fd32ca3f05bf1d713bb97e4

In case the warning -Werror=conversion is active with GCC, the warnings
about "conversion from A to B may change value" lead to a compilation
error. This explicitly convert the values to address these warnings.





In case the warning -Werror=conversion is active with GCC, the warnings
about "conversion from A to B may change value" lead to a compilation
error. This explicitly convert the values to address these warnings.







Sprinkle some constexpr around to make Jason happy
2024-09-13T14:40:11+00:00

Martin Hořeňovský

2024-09-13T09:16:20+00:00

18df97df00848e91bfe1b63408bba19f8b8237ae

Most of these will not matter in practice due to C++14 imposing
significant limitations on what else we can make constexpr, and we cannot
have references outliving the constexpr context either way.





Most of these will not matter in practice due to C++14 imposing
significant limitations on what else we can make constexpr, and we cannot
have references outliving the constexpr context either way.







Slight improvement to computing clock resolution in benchmarking
2024-07-22T08:54:16+00:00

Martin Hořeňovský

2024-07-22T08:08:59+00:00

7af96bbb226930900b4b4902d7494c03bbba59c4