Re: std.allocator: false pointers

[Andrei Alexandrescu via Digitalmars-d]

On 5/2/14, 10:15 AM, Orvid King via Digitalmars-d wrote:

Well, in a 64-bit address space, the false pointer issue is almost
mute, the issue comes in when you try to apply this design to 32-bit,
where the false pointer issue is more prevelent. Is the volume of
memory saved by this really worth it?

It's the time savings that are most important.

Another thing to consider is that this makes it impossible to
pre-allocate blocks of varying sizes for absurdly fast allocations via
atomic linked lists, in most cases literally a single `lock cmpxchg`.

Those can be accommodated I think.


Andrei