We've adapted a tuple implementation; however, that tuple doesn't know that there's "another tuple" it needs to be compatible with... we do know. So, let's try and make kat::tuple usable wherever on the host side we can use std::tuple; and vice-versa.
We've adapted a tuple implementation; however, that tuple doesn't know that there's "another tuple" it needs to be compatible with... we do know. So, let's try and make
kat::tuple
usable wherever on the host side we can usestd::tuple
; and vice-versa.