Damien L-G
Damien L-G
Do you have a stack trace?
Where is that `"ERROR : Process exiting while Kokkos::Threads is still initialized"` emitted from? It does not look like an error message we produce.
I was looking in `develop` but you're right I see in 4.2
What do you mean by "fixi(ng) the move semantics of `Kokkos::View`"? Are you specifically looking at the moved-from state?
Closing in favor #6636
No. Our mdspan implementation works with C++17.
| AppName | Area | Institution | Website | Status | Uses KokkosKernels | Contact Name | Contact Email | | --- | --- | --- | --- | ---...
I agree that it would be nice to check the QOI of backends with respect of error messages when constructing/deleting Kokkos objects and invoking functions before Kokkos::initialize or after Kokkos::finalize....
Please provide a rational explaining why this is needed (in the description)
Digging more into this, we define `UnorderedMapInvalidIndex` https://github.com/kokkos/kokkos/blob/a41dba5860c019f503822854f5ba8485937e1733/containers/src/Kokkos_UnorderedMap.hpp#L43 and `size_type` is always unsigned https://github.com/kokkos/kokkos/blob/a41dba5860c019f503822854f5ba8485937e1733/containers/src/Kokkos_UnorderedMap.hpp#L232 so users can already compare the value returned by `find()` with `UnorderedMapInvalidIndex`. ```C++ auto index =...