www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - [Issue 23318] New: GCAllocator should not implement deallocate


          Issue ID: 23318
           Summary: GCAllocator should not implement deallocate
           Product: D
           Version: D2
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: phobos
          Assignee: nobody puremagic.com
          Reporter: snarwin+bugzilla gmail.com

Currently, a container instantiated using GCAllocator is not usable in  safe

dependency "emsi_containers" version="~>0.9.0"
import containers.dynamicarray;
import std.experimental.allocator.gc_allocator;

void main()  safe
    auto a = DynamicArray!(int, GCAllocator)();

Attempting to compile the above program produces the following error message:

onlineapp.d(9,10): Error: ` safe` function `D main` cannot call ` system`
destructor `containers.dynamicarray.DynamicArray!(int, GCAllocator,

The destructor is  system because it calls GCAllocator.deallocate, which in
turn calls GC.free [1]--in other words, because the container is freeing its
memory manually, rather than relying on the GC to free it automatically.

Since GCAllocator is intended to be std.experimental.allocator's interface to
D's built-in GC, it should match the behavior of the GC as closely as possible.
In particular, a container instantiated with GCAllocator should behave the same
way as a container that allocates with `new` directly w.r.t. memory management.
Such a container would *not* free its memory manually on destruction.

To resolve this inconsistency, GCAllocator.deallocate should be removed.


Sep 02 2022