Deprecating Allocating Functions In std.string

Jack Stouffer via Digitalmars-d digitalmars-d at
Wed Nov 4 08:17:27 PST 2015

Looking through the source code of std.string, a lot of the 
functions that allocate have range based non-allocating 
alternatives that accomplish the same task. I'm wondering if 
there is any specific reason to keep the allocating versions 
around? If there are two functions in the same module that 
perform the same task, why not do the cycle of 
deprecation->remove docs->remove on the allocating version, as 
the other function is clearly better. Also, it's more GC handling 
code that would be removed, which is good for PR reasons.

More information about the Digitalmars-d mailing list