catch3/src/catch2/internal, branch constexpr_approx Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Handle ANSI escape sequences when performing column wrapping (#2849) 2024-05-04T21:43:52+00:00 Jeremy Rifkin 2024-05-04T21:43:52+00:00 8ce2426e53b2596a9823b4a314f72f1c3b30be82 This PR adds functionality to skip around ANSI escape sequences in catch_textflow so they do not contribute to line length and line wrapping code does not split escape sequences in the middle. I've implemented this by creating a AnsiSkippingString abstraction that has a bidirectional iterator that can skip around escape sequences while iterating. Additionally I refactored Column::const_iterator to be iterator-based rather than index-based so this abstraction is a simple drop-in for std::string. Currently only color sequences are handled, other escape sequences are left unaffected. Motivation: Text with ANSI color sequences gets messed up when being output by Catch2 #2833. 
This PR adds functionality to skip around ANSI escape sequences in catch_textflow so they do not contribute to line length and line wrapping code does not split escape sequences in the middle. I've implemented this by creating a AnsiSkippingString abstraction that has a bidirectional iterator that can skip around escape sequences while iterating. Additionally I refactored Column::const_iterator to be iterator-based rather than index-based so this abstraction is a simple drop-in for std::string.

Currently only color sequences are handled, other escape sequences are left unaffected.

Motivation: Text with ANSI color sequences gets messed up when being output by Catch2 #2833.
 Explicitly silence Wnon-virtual-dtor in Decomposer and MatchExpr 2024-04-30T21:51:36+00:00 Martin Hořeňovský 2024-04-30T19:08:35+00:00 fa5a53df17303339eff8fda5cae0b601af207085 Closes #2854 
Closes #2854
Handle active Sections for fatal errors 2024-04-21T19:52:33+00:00 Altan Birler 2024-04-15T11:25:08+00:00 42fe78d0ba0eb33096a705e8f9c4814fd619eebd Closes #1210 When a signal is caught, the destructors of Sections will not be called. Thus, we must call `sectionEndedEarly` manually for those Sections. Example test case: ``` TEST_CASE("broken") { SECTION("section") { /// Use illegal cpu instruction __asm__ __volatile__("ud2" : : : "memory"); } } ``` 
Closes #1210

When a signal is caught, the destructors of Sections will not be called.
Thus, we must call `sectionEndedEarly` manually for those Sections.

Example test case:
```
TEST_CASE("broken") {
   SECTION("section") {
      /// Use illegal cpu instruction
      __asm__ __volatile__("ud2" : : : "memory");
   }
}
```
Fix build on ARM64EC (#2858) 2024-04-19T08:36:37+00:00 AgostonSzepessy 2024-04-19T08:36:37+00:00 f2320724a74f95d83f8c259e1a96cf2cd9a1d6aa Remove `#pragma intrinsic(_umul128)` because it doesn't work on ARM64EC and x64 works without it. Co-authored-by: Agoston Szepessy <agos@microsoft.com> 
Remove `#pragma intrinsic(_umul128)` because it doesn't work on
ARM64EC and x64 works without it.

Co-authored-by: Agoston Szepessy <agos@microsoft.com>
 Actually check for x64 target with MSVC 2024-04-13T20:51:17+00:00 Martin Hořeňovský 2024-04-13T20:51:17+00:00 029fe3b4609dd84cd939b73357f37bbb75bcf82f 






Fix ARM64 windows builds
2024-04-12T14:40:06+00:00

Martin Hořeňovský

2024-04-12T13:20:08+00:00

65794fd2b8fd05c2d5524acf44bc9ac2bad19d97

Apparently I looked at the docs for umulh when checking availability,
and umul128 is x64 only.





Apparently I looked at the docs for umulh when checking availability,
and umul128 is x64 only.







Explicitly outline TestRegistry destructor into .cpp file
2024-04-08T11:57:59+00:00

Martin Hořeňovský

2024-04-08T11:57:53+00:00

cd8f97e6c7f6aaf332992f83bf9d7ee7f357f85e

This fixes compilation issue with C++23 mode against libstdc++.

Closes #2852





This fixes compilation issue with C++23 mode against libstdc++.

Closes #2852







Fix assertion for const instance of std::ordering
2024-04-08T09:33:43+00:00

Martin Hořeňovský

2024-04-08T09:02:22+00:00

71b11c4e3328090d2ec72268299e3fb9e0ac3f8e

The issue was that `capture_by_value` was meant to be specialized
by plain type, e.g. `capture_by_value<std::weak_ordering>`, but
the TMP in Decomposer did not properly throw away `const` (and
`volatile`) qualifiers, before taking the value of `capture_by_value`.





The issue was that `capture_by_value` was meant to be specialized
by plain type, e.g. `capture_by_value<std::weak_ordering>`, but
the TMP in Decomposer did not properly throw away `const` (and
`volatile`) qualifiers, before taking the value of `capture_by_value`.







Optimize 64x64 extended multiplication implementation
2024-04-03T11:28:25+00:00

Martin Hořeňovský

2024-04-02T16:09:34+00:00

d99eb8bec8de53639540820ee2a6563b88c4ba8c

Now we use intrinsics when possible, and fallback to optimized
implementation in portable C++. The difference is about 4x when
we can use intrinsics and about 2x when we cannot.

This should speed up our Lemire's algorithm implementation nicely.





Now we use intrinsics when possible, and fallback to optimized
implementation in portable C++. The difference is about 4x when
we can use intrinsics and about 2x when we cannot.

This should speed up our Lemire's algorithm implementation nicely.







Use SizedUnsignedType_t to pick UnsignedType for uniform_integer_distribution
2024-04-03T11:27:10+00:00

Martin Hořeňovský

2024-04-03T10:29:51+00:00

f181de9df4c43f188ae932a412af32a0981c9067

The previously used `make_unsigned` approach combined with the overload
set of `extendedMult` caused compilation issues on MacOS platform. By
forcing the selection to be one of `std::uintX_t` types we don't need
to complicate the overload set further.





The previously used `make_unsigned` approach combined with the overload
set of `extendedMult` caused compilation issues on MacOS platform. By
forcing the selection to be one of `std::uintX_t` types we don't need
to complicate the overload set further.