On Tuesday, September 06, 2011 00:33:20 dsimcha wrote: > == Quote from Jonathan M Davis ([email protected])'s article > > > dsimcha, is there any reason not to start the review of the region > > allocator shortly? Does a review period of about 2 weeks, ending on > > Wednesday, the 21st sound good? > > - Jonathan M Davis > > Sounds perfect. Thanks. A few issues that I'd like mentioned in the > initial announcement because they need to be examined: > > 1. This is both a proposal for RegionAllocator and a proposal for a more > general allocator API in Phobos. The allocator API will be a structural > interface that includes the intersection of gcallocator and regionallocator > functionality. I don't have a more precise definition yet. Hopefully the > review process will hammer out whatever ambiguities remain. > > 2. Should we put this stuff in a std.allocators package, in a single > std.allocators module, or something else? > > 3. We definitely want a reap (combination region and heap) eventually, > though I don't have one yet. I want RegionAllocator to be reviewed for > anything that would make it unnecessarily hard to write other allocators on > top of it, most importantly reaps but also free lists, etc.
Can you provide a link to the current code and documentation so that I can post the start of the review? And do you want to provide a more in depth description than ----------- std.regionallocator (A segmented stack/region memory allocator, by me. I'd like to fast-track this because it's used by two of the GSoC projects that were done this summer so getting it into Phobos would simplify things.) ----------- which is what you previously posted? - Jonathan M Davis
