On 10/9/14, 9:00 AM, Dicebot wrote:
On Thursday, 9 October 2014 at 15:59:12 UTC, Andrei Alexandrescu wrote:
"Dicebot" <pub...@dicebot.lv> wrote:
On Thursday, 9 October 2014 at 15:00:02 UTC, ixid wrote:
Multiple approaches to how library functions can handle memory.
As long as it allows us avoid creating new GC roots and keep using GC
for
all allocations at the same time.
To clarify: calling GC.free does remove the root, correct?
Not before it creates one. When I mean "avoid creating new GC roots" I
mean "no GC activity at all other than extending existing chunks"
That's interesting. So GC.malloc followed by GC.free does actually
affect things negatively? Also let's note that extending existing chunks
may result in new allocations.
Andrei
