Re-export volatile_copy_memory in `core::ptr`?

language design
1

Is there a reason that volatile_copy_memory and friends are not re-exported in core::ptr along with write_volatile and read_volatile?

2

I don’t think there’s a reason - seems fine to expose as core::ptr::copy_volatile and similarly for the nonoverlapping variant.

3

OK, cool. A project I’m working on might need that. If so, I’ll throw up a PR.

4

Related: Opened up this issue to do the same with volatile_copy_memory_nonoverlapping.

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.