sliwowitz

> @sliwowitz ping? I like it. BTW, tangentially related to this PR - there's been some discussion about moving the RNGs to a separate library, we might want to revisit...

Yes. I got stuck on the `KernelExecutionBenchmarkFixture` idea. I wanted to make it a general object usable for other benchmarks than the simple example benchmark, but it's still unclear to...

I'd vote for the JSON reporter as it could make the output both machine- and human-readable :-)

Same problem on Gnome 2.36.1. After running a fullscreen application (Steam games), Caffeine gets stuck and doesn't respond to mouse click. I have disable and re-enable it to make it...

I would agree this is a separate issue mostly because already wrap *some* of the vendor RNGs. There's Xorwow for CUDA/HIP and there are several generators from STL. Originally I...

> Didn't we have a discussion in the past to take out the RNG parts of alpaka and move them to a separate library? Yes. Initially, I was implementing Philox...

> Sure, but what if you really just need a bunch of random numbers with the fastest solution on each backend? And you would not care about determinism across backends....

There's also https://github.com/alpaka-group/alpaka/pull/1723 which I've just rebased on top of actual develop. It uses Catch2 for benchmarking infrastructure (thus integrated with e.g. ctest). I tried to implement a generaic fixture...

I suppose so. I've looked into the current `Vec` test, and it seems we're only testing integral types. Was this class ever supposed to handle floating point values?

Seems @bernhardmgruber's idea works fine too. Does anyone have tips on what kind of additional tests to write for this? Maybe extend the [current tests](https://github.com/alpaka-group/alpaka/blob/develop/test/unit/vec/src/VecTest.cpp) so that they'd consturct `Vec`s...