You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But if my_function does only pass the arrays to a third function, then I would need a plain mdspan without any host or device annotation. Shall we work with plain std::experimental::mdspan, or do we want to allow host_device_accessor that has no information about where the data is accessible?
The text was updated successfully, but these errors were encountered:
Currently neighbors::detail::utils::subsample takes the dataset
input
as plain pointer.The
input
shall be replaced with an mdspan. This is not done in #2077, because the following question needs to be clarified:What is the right way to map a pointer for raft
mdspan
API, if I do not know (and do not care) whether the pointer is on host or device?One way to do that is to query the pointer attribute and map it accordingly
But if
my_function
does only pass the arrays to a third function, then I would need a plainmdspan
without any host or device annotation. Shall we work with plainstd::experimental::mdspan
, or do we want to allowhost_device_accessor
that has no information about where the data is accessible?The text was updated successfully, but these errors were encountered: