Is there a reason that volatile_copy_memory and friends are not re-exported in core::ptr along with write_volatile and read_volatile?
volatile_copy_memory
core::ptr
write_volatile
read_volatile
I don’t think there’s a reason - seems fine to expose as core::ptr::copy_volatile and similarly for the nonoverlapping variant.
core::ptr::copy_volatile
OK, cool. A project I’m working on might need that. If so, I’ll throw up a PR.
Related: Opened up this issue to do the same with volatile_copy_memory_nonoverlapping.
volatile_copy_memory_nonoverlapping