Phobos addition formal review: std.experimental.allocator

[Baz via Digitalmars-d]

On Tuesday, 30 June 2015 at 06:07:14 UTC, Baz wrote:
> On Friday, 26 June 2015 at 15:23:25 UTC, Alex Parrill wrote:
>> On Friday, 26 June 2015 at 14:56:21 UTC, Dmitry Olshansky 
>> wrote:
>>> [...]
>>
>> Yea, VirtualAlloc seems like a better fit. (I don't actually 
>> know the windows API that well)
>>
>>> [...]
>>
>> Here's the paragraph I'm reading:
>>
>> Mapped views of a file mapping object maintain internal 
>> references to the object, and a file mapping object does not 
>> close until all references to it are released. Therefore, to 
>> fully close a file mapping object, an application must unmap 
>> all mapped views of the file mapping object by calling 
>> UnmapViewOfFile and close the file mapping object handle by 
>> calling CloseHandle. These functions can be called in any 
>> order.
>
> https://github.com/andralex/phobos/pull/17

By the way, the ddoc comment for mmap needs to be updated (not 
posix only).
I don't know what to write because initially i just wanted to 
build allocator under win and proposed to the mmap allocator for 
win without thinking more...

currently under win the only difference between a simple malloc 
is that the allocation happen on commitment...previously it was 
really an anonymous memory mapped file...).