Heads-up: upcoming instabilities in std.experimental.allocator, and what to do

[Luís Marques]

On Thursday, 30 November 2017 at 19:01:02 UTC, Andrei 
Alexandrescu wrote:
> Another possible work item was raised by 
> https://github.com/dlang/phobos/pull/5879. Currently, 
> allocators traffic in void[]. When I first designed allocators, 
> I considered using ubyte[] instead. Using void[] is somewhat 
> closer to the intent of allocators - that memory is meant to be 
> used for storing anything. However, using void[] makes it 
> difficult to express the fact that allocate() is a safe 
> function for virtual all allocators. So we may switch to 
> ubyte[] to express that at the lowest level we're trafficking 
> chunks of octets. This is not a big design change, but it's 
> bound to break code.

That argument should also apply to e.g. std.file.read.