Oliver Stöneberg
Oliver Stöneberg
Ah, you opened the other PR against a branch of mine which I already deleted. Didn't even realize that. My tests have finally been merged and I pushed the first...
This is still in my scope but I got side tracked with some more fundamental stuff again. I also didn't feel like looking at creating new Python tests in the...
I think we (I?) disabled these to speed up the run-time of the CI. But a Visual Studio debug build enables run-time checks which might detect additional issues - see...
The debug build is too slow to finish the `test_crash_array_in_namespace` Python test in time.
Ugh. That seems to overload the runner causing one of the performance tests to fail more often. This might apply to other code relying on `nproc`.
Clang 20 reports less warnings but it is still quite noisy for our code. I will clean this up and try to land some related stuff beforehand.
Let's re-visit this with a future version of Clang. Closing as we should start from scratch.
> Just stating the fact is probably not enough to steer users in the right direction. And if 'pass by value + move' is used, the object will still be...
There is just too many possible solutions to include it at all. So no verbose message at all would be better. Maybe we can just reword the message by including...
> sorry are there that many possible solutions? on top of the mentioned ones: - rvalues - forwarding - perfect forwarding - explicitly moving without involving `std::move()` - possible modern...