https://issues.dlang.org/show_bug.cgi?id=19164
--- Comment #7 from Nathan S. <n8sh.second...@hotmail.com> --- The name "enforceMalloc" was chosen to be similar to "enforce" which throws an exception if its argument is false. The idea being "enforceMalloc" is like a shorthand way of writing: "auto ptr = malloc(sz); enforce!OutOfMemoryError(ptr);" >If anyone in five years time adds something else to Phobos that uses >those functions, how are they to know they shouldn't pass 0 to them? They can know by opening std.internal.memory and looking at what `enforceMalloc` does. If they don't know then they should not use it! --