On 2013-09-24 02:03, H. S. Teoh wrote:
I thought Walter's DIP already addresses the issue of replacing the default allocator?http://wiki.dlang.org/DIP46 I get the feeling that we don't have a good handle on the fundamental issues, though. Having a stack for managing the default allocator works for the simpler cases, but it's unclear how things would interact once you throw in other requirements, like class/struct-scoped allocators, block scoped allocators inside closures, user-specified allocators that must interact with the foregoing, etc..
Why not just let the user set the allocator explicitly, see: http://forum.dlang.org/thread/[email protected]?page=2#post-l1oqp2:2429fg:241:40digitalmars.com -- /Jacob Carlborg
