Brook Heisler

Yeah, this will be tricky alright. I haven't planned out a design for this. The only time we can be sure that it's safe to drop either the host-side or...

Yeah, that fits really well with how I was planning to handle futures. See, it's not zero-cost to create a Future tied to a CUDA stream - you have to...

Slight problem with that: [Link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=585395423e032685b439c9c9d519d141). Scheduling multiple copies using the same buffer is completely safe as long as they're all on the same stream, but this implementation disallows it.

I'd be very wary of unsafe black magic in this case - we could end up introducing undefined behavior while trying to hide other undefined behavior. Anyway, [this](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=5b000b51631b21035e8112f581c66ed9) is kinda...

Page-locked memory all handled by the driver. You call a certain CUDA API function to allocate and free page-locked memory. The driver tracks which memory ranges are locked and uses...

DeviceCopy is for structures that can safely be copied to the device (ie. They don't manage host-side resources or contain pointers that are only valid for the host). It has...

> AsyncMemcpy cannot take T: DeviceCopy anymore. Could you elaborate more on this? Why not?

> Hey, I'm really interested in this feature! (I'm porting my hobby raytracer to rustacuda) Thanks for your interest, and thanks for trying RustaCUDA! Yeah, I'd be interested in pull...

Hey, thanks for your interest! Yes, this is still open. I meant that we should remove `unwrap` from the examples in the rustdoc comments. I'll update the description to clarify.

Please do!