Use case: eliminate hidden allocations in buildPath
Marco Leise
Marco.Leise at gmx.de
Sat Dec 7 23:41:43 PST 2013
Am Sat, 7 Dec 2013 13:27:07 -0500
schrieb Michel Fortin <michel.fortin at michelf.ca>:
> […] The way to fix that with an output range would be to have
> have a "reserve" function telling the range "prepare yourself to
> receive that much data", which may or may not do something depending on
> the kind of output range it is.
This could even preallocate blocks on a filesystem for file
record based output ranges. (In order to avoid
file fragmentation on mechanical disks.)
--
Marco
More information about the Digitalmars-d
mailing list