rustacuda is no longer maintained, and includes all of rustacuda and most of the custom patches we are using in rust-cuda.
However, the following incompatibilities remain:
[ ] cust_core::DeviceCopy now has Copy as a supertrait. This is both too weak and too strong for rust-cuda. There is no workaround. If cust doesn't change this requirement, no migration can occur. https://github.com/Rust-GPU/Rust-CUDA/issues/124
[ ] Stream::wait_event takes an owned Event and Events cannot be cloned or inspected. This could be fixed by falling back to raw FFI for all usages. https://github.com/Rust-GPU/Rust-CUDA/issues/110
rustacudais no longer maintained, and includes all ofrustacudaand most of the custom patches we are using inrust-cuda.However, the following incompatibilities remain:
cust_core::DeviceCopynow hasCopyas a supertrait. This is both too weak and too strong forrust-cuda. There is no workaround. Ifcustdoesn't change this requirement, no migration can occur. https://github.com/Rust-GPU/Rust-CUDA/issues/124Stream::wait_eventtakes an ownedEventandEvents cannot be cloned or inspected. This could be fixed by falling back to raw FFI for all usages. https://github.com/Rust-GPU/Rust-CUDA/issues/110Stream::add_callbackno longer provides access to the current stream status. The callback might just not be scheduled anymore if an error occurred (which could result in a never-resolving async future), or do something even worse. This could be fixed by falling back to raw FFI. https://stackoverflow.com/questions/56448390/how-to-recover-from-cuda-errors-when-using-cudalaunchhostfunc-instead-of-cudastr