On Wednesday, 20 April 2016 at 20:07:31 UTC, Nordlöw wrote:
On Wednesday, 20 April 2016 at 16:08:32 UTC, Lass Safin wrote:
core.memory.GC.setAttr can set attributes for a block of
memory, with which you can set the attribute NO_SCAN, which as
it implies, forces that no scan be done in the particular
block of memory.
This can be used to insure that the GC doesn't mark blocks not
alive as alive.
Is this needed
- *only* for regions allocated with GC.malloc or
- *also* for memory allocated with non malloc/calloc/realloc?
NO_SCAN should probably be set for all types of memory blocks. I
don't even know if the GC actually scans mallocated memory in the
first place.
