Hi Thiago,

On Thu, Oct 30, 2025 at 07:27:38AM -0700, Thiago Macieira via Std-Proposals wrote:
> On Wednesday, 29 October 2025 14:24:23 Pacific Daylight Time Thiago Macieira
> via Std-Proposals wrote:
> > I disagree because I don't want to wait for that operation. I want
> > relocations now. In fact, I want them in 2005, when Qt began doing them
> > anyway. It's memcpy/memmove, period.
>
> Oh, and realloc(). That's actually the most important one.
>
> I'll accept a replacement function if realloc() can't be fixed.

I don't know if realloc(3) has any issues in C++, but if you mean the
issues that C also has, we're in the process of fixing them.

See:
<https://www.austingroupbugs.net/view.php?id=1949>
<https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3621.txt>


Have a lovely day!
Alex

> But there needs
> to be something that resizes an allocated memory block for trivially-
> relocatable objects and has a good chance of not moving the memory block
> (resize-in-place). Was that added by P2786?
>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> Principal Engineer - Intel Data Center - Platform & Sys. Eng.



> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals

-- 
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).