On Wednesday, 30 October 2013 at 12:39:18 UTC, Joseph Rushton
Wakeling wrote:
On 30/10/13 01:38, inout wrote:
This has almost nothing to do with an allocator.
My impression was that std.allocator as-is was designed to
create a toolkit for developers to build different memory
management strategies into their applications. Is there any
reason why that should exclude implementing ref-counting
approaches?
"memory allocation strategy" != "memory management strategy",
though those can be possibly coupled. Ref-counting can be done on
top of any allocation strategy that support deterministic
deallocattion.
