Expose cuMemcpyDtoH_v2 in cust #45
Description
In the latest version (0.3.0) of cust cuMemcpyHtoD_v2 was exposed as cust::memory::memcpy_htod. This avoids the need for reaching into cust_raw and allows using cust::error::CudaResult instead of error codes.
Should cuMemcpyDtoH_v2 be exposed in a similar manner to enable the features above for device to host memcpy as well?