In some files (e.g. tuple.hpp), we are inconsistent in the use of kat::move() and kat::forward() vs std::move() and std::forward().
The kat versions of these functions are not necessary, as nVIDIA makes an exception for their std versions and interprets them as __host__ __device__ functions.
So, let's just switch everything to the std versions. Howerver, we'll leae the kat versions within an #ifdef guard: KAT_DEFINE_MOVE_AND_FORWARD.
This is two issues in one:
tuple.hpp
), we are inconsistent in the use ofkat::move()
andkat::forward()
vsstd::move()
andstd::forward()
.std
versions and interprets them as__host__ __device__
functions.So, let's just switch everything to the
std
versions. Howerver, we'll leae the kat versions within an#ifdef
guard:KAT_DEFINE_MOVE_AND_FORWARD
.