malloc will generally do lazy copy-on-write above a certain limit; it was 128kb for glibc last time I checked.
> why can't I have an error checking malloc()
reallocarray is becoming the de-facto standard for that.
> why can't I have a calloc() that allocates the memory up front and doesn't zero it out?
Er, malloc?
malloc will generally do lazy copy-on-write above a certain limit; it was 128kb for glibc last time I checked.
> why can't I have an error checking malloc()
reallocarray is becoming the de-facto standard for that.
> why can't I have a calloc() that allocates the memory up front and doesn't zero it out?
Er, malloc?