[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.BSM.4.64L.2510311215400.9149@herc.mirbsd.org>
Date: Fri, 31 Oct 2025 12:16:39 +0000 (UTC)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
cc: libc-alpha@...rceware.org, "Arthur O'Dwyer" <arthur.j.odwyer@...il.com>,
Jonathan Wakely <jwakely@...hat.com>,
Thiago Macieira <thiago@...ieira.org>
Subject: Re: realloci(): A realloc() variant that works in-place
Alejandro Colomar dixit:
>A discussion within the C++ std-proposals@ mailing list triggered the
>discussion about the need for a realloc() variant that works in-place,
>that is, that doesn't move the address of the memory, and thus that
>doesn't invalidate existing pointers derived from it.
How is that supposed to work if you want to grow the
allocation?
This seems like increasing burden on the implementation
for everyone, just for niche corner use cases.
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
