Date: Tue, 11 Nov 2025 14:16:19 -0800
On Tuesday, 11 November 2025 07:45:38 Pacific Standard Time Sebastian Wittmeier
via Std-Proposals wrote:
> An implementation could decide to decrypt the whole memory, not just the
> vptr.
Either memmove() already does that - in which case the relocation is trivial -
or it doesn't and therefore one can't use realloc() with this type.
> So throwing away data is not an option in that case.
>
> Or at least the part of memory without pod types, e.g. all pointers.
The pointers would remain valid, so long as they are not self-referential
pointers (like libstdc++'s std::string).
via Std-Proposals wrote:
> An implementation could decide to decrypt the whole memory, not just the
> vptr.
Either memmove() already does that - in which case the relocation is trivial -
or it doesn't and therefore one can't use realloc() with this type.
> So throwing away data is not an option in that case.
>
> Or at least the part of memory without pod types, e.g. all pointers.
The pointers would remain valid, so long as they are not self-referential
pointers (like libstdc++'s std::string).
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Received on 2025-11-11 22:16:29
