Char Aznable

I also tried eliminating the all-zeros columns but that didn't help

>As I understand the ticket, you're fine in having just Boost.Test with CMake's ability to fetch the needed additional dependencies. Is that correct? Actually no. What I wanted is to...

To give this some context, the intended usage was actually `Kokkos::vector` and the same error was found when calling the vector's `push_back()` method.

Not sure if this is related but if we do ```c++ Kokkos::View vCopy("vCopy", v.extent(0)); Kokkos::deep_copy(vCopy, v); ``` instead of the resize() call then it gives a different error: ```c++ Kokkos::Impl::SharedAllocationRecord...

Not sure if this is related but something like this will also throw `Constructing View and initializing data with uninitialized execution space`: ```c++ int main(int argc, char* argv[]) { Kokkos::initialize(argc,argv);...

I suspect the main problem is that `Kokkos::Bitset` and `Kokkos::vector` both lack a device default ctor. I tried patching this up by: ```c++ diff --git a/containers/src/Kokkos_Bitset.hpp b/containers/src/Kokkos_Bitset.hpp index ea1d6dde..bc296eb4 100644...

There are actually deeper problems. There are Kokkos APIs like `Kokkos::volatile_load` that makes implicit assumption about input type being device-side constructible and these APIs are used all over the place...

I believe this is still active. The workaround on https://github.com/kokkos/kokkos/wiki/View#6233-i-really-want-a-view-of-views-what-do-i-do can be implemented as specialization of `Kokkos::Vector`. I can take a look at this when I have the time

I have similar issue when writing a snippet for c++.

In GoolgeTest, there is the "result_listener" to customize the output message upon a matcher returning false. I wonder if Catch can do something similar