But alas: > The reaction of the Java developer community to our report is somewhat disappointing: instead of using our fixed (and verified!) version of mergeCo

But alas: > The reaction of the Java developer community to our report is somewhat disappointing: instead of using our fixed (and verified!) version of mergeCollapse(), they opted to increase the allocated runLen “sufficiently”. As we showed, this is not necessary. In consequence, whoever uses java.utils.Collection.sort() is forced to over allocate space.