Re: [boost] copy on write for std containers

"Jeffrey Lee Hellrung, Jr." <jhellrung@ucla.edu> wrote in message news:4CFADA65.40708@ucla.edu...

I think the point is that copy-on-write is rarely optimal, often suboptimal, and increases complexity; hence it should not be encouraged.

increases complexity -- wrong -- I only replaced the matching types -- the using code was not modified. The number of lines for the wrapper are minimal -- I only implemented the methods I'm using. I don't care about complexity the compiler has to manage. I care about the complexity I have to manage. I could introduce some filtering to avoid storing identical instances which would even more decrease the memory foot print.