On 4/2/18 5:16 PM, Per Nordlöw wrote:
On Monday, 2 April 2018 at 20:43:01 UTC, Alexandru Jercaianu wrote:
I am not completely sure how to solve this, but maybe we can find some
clues here .
It seems like we should use addRoot on the buffer returned by
GC.instance.allocate to keep it alive.
Then, we can use addRange on each node after allocation and somehow
use 'TypeInfo' to trigger destructors.
I'll dig into this more tomorrow and come back with a better answer.
How can there not be a documented answer for this question, given that
std.experimental.allocator has been in Phobos for 2 years?
Has std.experimental.allocator only been used for allocating `struct`s?
Is the Region allocator especially misfit for constructing classes?
Since a while, the GC also calls struct destructors, so it's likely to
be a problem for both.
Note, addRoot and addRange will NOT call the destructors appropriately.
It will just prevent those memory areas from getting collected. The
memory shouldn't be collected anyway because RegionAllocator should have
a reference to it.
The only way it will get destroyed is removing the root/range, and then
it will get collected just like any other GC block -- same as it is now.
It looks like std.experimental.allocator assumes you will manually
destroy items (possibly via dispose), it has no mechanism to say "here's
how to destroy this memory I'm allocating if you happen to collect it".