On 2011-09-01 16:28, 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.)
Docs:
http://cis.jhu.edu/~dsimcha/d/phobos/std_regionallocator.html
(I forgot to compile the docs to gcallocator. I'll do that at some point, but I
expect the vast majority of the discussion to be about regionallocator anyhow,
since gcallocator is just a trivial wrapper.)
One more thing: std.regionallocator should **probably** be
std.allocators.regionallocator, but I'm too lazy to change this until we
officially settle on this as a name.
I think it's unnecessary to repeat "allocator" in the module name if the
module is already in the allocators package.
--
/Jacob Carlborg
