Jan Möller

I think this is part of a (much) bigger problem: I find myself writing (and hence testing) more and more constexpr code. And for any at least partially constexpr-enabled type...

Often, constexpr code is very inefficient at runtime, which is why an implementation might choose to (partially) delegate to different implementation strategies depending on std::is_constant_evaluated() / if consteval. In this...

@krzysztof-jusiak Right, that's the same kind of workaround I was doing with Catch above. But, what would be really cool is if the following just worked: ```c++ "std::vector"_test_both_at_runtime_and_compiletime = []...

Please also consider #2298 as a relevant issue here.