Sharing in D

[downs]

superdan wrote:
> Sean Kelly Wrote:
> 
>> All that said, I believe it's entirely possible to write performance-critical code in D so long as the
>> programmer is careful about memory allocation.  And as Walter has said before, because even
>> malloc is not time-constrained the same goes for any use of dynamic memory--GCs just magnify
>> the issue.  Server apps in Tango, for example, don't allocate any memory at all once initialization
>> is complete.  This is why they tend to be so blisteringly fast.  It's also why Tango is designed the
>> way it is--not always super-convenient for run of the mill apps programming, but quite scalable
>> for high-end work.  By contrast, I'd argue that Phobos is the opposite.
> 
> i agree. std.algorithm i sleep with under my pillow. but std.xml. what a sick piece of shit that is. if they tried to make it slow on purpose they couldn't have succeeded better. std.xml must go.

Heh. Want to have some fun, take a look at std.zip.

Then realize that, unless you unpack every member every time, the members you didn't unpack will still have their compressed data overwritten by a compressed version of the expanded data (which is "").

Then weep.

 --downs, immensely glad the zip archive he noticed this on was backed up in SVN.