[RFC] Removal of allocator::construct / destroy vs our containers

[Paolo Carlini]

Hi,

>> I'm thinking of applying the patch even earlier than Toronto, that 
>> way, in case construct / destroy will stay, we are ok, 
>> performance-wise, anyway. Otherwise, in case construct / destroy will 
>> actually go away, it would be only matter of tweaking a bit the 
>> posted patch, matter of a few lines. That way we could relax, not 
>> having to remember for months to apply this last patch in case 
>> construct / destroy eventually stay...
>
> This would be my preference as well.

Ok, therefore I have slightly adjusted the patch - and extended the 
tweaks for rope, all the other containers are already ok - and regtested 
it again on x86-linux. I mean to apply it very soon.

Paolo.

///////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CL_cons_dest_byref_2
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20070504/3cab8566/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_cons_dest_byref_2
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20070504/3cab8566/attachment-0001.ksh>