On 09/01/2011 04:28 PM, dsimcha wrote:
== Quote from Lars T. Kyllingstad ([email protected])'s
Anyway, I personally don't think the region allocator should have its own
module, it should be in std.allocator or something like that. AFAIK, the
plan is to have multiple allocators adhering to the same interface. But
that's probably a discussion for the review. ;)
-Lars
If we want to do that,
Code:
https://github.com/dsimcha/TempAlloc
(regionallocator.d is the main proposal, gcallocator.d is a throw-in wrapper
around the garbage collector to create a standard allocator interface to it.
The
repo is named TempAlloc because that's what the module used to be called before
its overhaul.)
[snip.]
Allocating a class or struct instance with a given allocator seems not
to be part of the standard allocator interface. Why is that?
(their implementations would be almost identical between most
allocators, but the same could be said about the newArray etc. member
functions)
I am really looking forward to having a region allocator. Thanks!
