Are implementations allowed to have
malloc allocate far more memory than requested, so it can avoid overhead for later small allocations?
In my experience, no one ever allocates single objects on the heap due to how costly it is, usually writing small object allocators or simply creating large arrays where possible. So an implementation doing this for the programmer feels like it should be an easy ergonomics/performance feature to implement.
Do compilers already do this, or does the standard or another issue prevent this?