Re: memcpy, memset, memcmp and friends in the D Runtime

[Daniel Murphy]

"monarch_dodra"  wrote in message 
news:pdzhmmnjxclrjtkgu...@forum.dlang.org...

I think arguably, there should be D equivalents of the C runtime 
functions, if only for the added safety of slices (for example, memchr 
could be 100% certifiably safe), and to avoid the rampant deduplication of 
things as in the above, because of CTFE.

The utility of a 'slightly safer' layer between the C functions and the 
phobos range-based functions is questionable IMO.  eg in cases where memcpy 
on arrays is safe, phobos' copy would likely optimize to the exact same 
code.