== Quote from Lars T. Kyllingstad ([email protected])'s article > 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
My concern with this is threefold: 1. A single module with a whole bunch of allocators would get quite unwieldy. std.regionallocator by itself is about 2k lines. 2. I don't want to give the impression that I've implemented a comprehensive suite of allocators as std.allocator would imply. I haven't. I've implemented one important one to kick things off, plus a trivial wrapper. 3. I think any new allocator is a big enough thing that it should go through a full-fledged "new module" review.
