Bug 16250 – GCAllocator should be at least @safe, nothrow

A common pattern for future APIs would be to allow to pass-in a custom Allocator and have @safe and nothrow code if the GCAllocator was used. Ideally I hope that the language might ease the use of custom allocators, but being conveniently able to switch between safe and non-safe fast code would be a good start. See e.g. this simple test for an example: nothrow unittest { import std.experimental.allocator: dispose, makeArray; import std.experimental.allocator.gc_allocator: GCAllocator; auto Allocator = GCAllocator.instance; auto safeFun() @safe { int[] arr = Allocator.makeArray!int(2); assert(arr == [0, 0]); return arr; } Allocator.dispose(safeFun()); } Imho this test could also be `pure`, but that's not really important there . There's is already an ongoing PR, but that lost its motion and needs to be revived. https://github.com/dlang/phobos/pull/3891 For no required shared in the GCAllocator, there is another ongoing effort: https://github.com/dlang/phobos/pull/4288

supported with https://github.com/dlang/phobos/pull/4680 https://github.com/dlang/phobos/pull/4681 https://github.com/dlang/phobos/pull/4682 https://github.com/dlang/phobos/pull/4683