On Wed, 29 Oct 2025 at 16:27, Sebastian Wittmeier via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> Another possibility is not to allow memcpy/memmove for trivially relocatable objects, but only make it work over relocation functions and keyword.
>
>
>
> Then memcpy/memmove don't have special behavior, but you are also not to allowed to assume byte identity or copy/move manually.

That's what we currently have. There are reasons why we have those
relocation functions, including that vtbl re-signing.