__rvalref overloads causing ambiguities

Paolo Carlini pcarlini@suse.de
Thu Jul 28 08:50:00 GMT 2005


Hi Chris,

>Here is an attempt at a patch to fix the rvalref ambiguities.
>  
>
Excellent. I'm going to test the patch a little further on a couple of
machines and, if everything goes well, will commit it to the branch
before leaving (will be in vacations 'til mid of August)

>I decided to change the constructors as well as the operator=. The
>constructors weren't causing a problem with this testcase, as there are
>already at least 2 standard-supplied constructors for each container
>(one taking the container, one taking an allocator). However templating
>them might stop other problems later. If someone with more template-foo
>than me thinks it would be safer to leave them as-is, I'm happy to
>change them back.
>  
>
Ok.

>Johnathan: I assume you a) have no problems with being put on the
>changelog, and b) I referenced you correctly?
>  
>
Very kind of you: FWIW, I agree that Jonathan did a great job, stressing
v7 together with Boost and preparing a reduced testcase. I believe the
reference is ok, at least identical to the other ones.

Paolo.



More information about the Libstdc++ mailing list