On Monday, 30 December 2013 at 18:22:22 UTC, Chris Cain wrote:
Sounds pretty dangerous to me. I wouldn't really describe that as "transparent" either. If it's working for you in C++, that's great. I wouldn't count on D adopting such an approach, however.
Well, either that or using a thread local variable setting the current pool, I assume objective-c does that.
I think in the near future there's going to be a standard "allocator interface" (std.allocator) which will allow you to easily use different allocation schemes depending on what you're doing.
Ok. :) as long as I don't have to pass the allocator around,mwhich is tedious.
