Re: __rvalref overloads causing ambiguities

[Paolo Carlini <pcarlini at suse dot de>]

chris jefferson wrote:

>        * @param x A %vector of identical element and allocator types
>        *
>        * The newly-constructed %vector contains the exact contents of @a x.
>-       * The contents of x are a valid, but unspecified vector.
>+       * The contents of x are a valid, but unspecified vector. This
>+       * constructor is templated to avoid it being used when deducing the
>+       * list of types convertable to vector.
>
Careful with spellings: convertible vs convertable.

>Comments? I'm expecting the first of these to go down better, so unless
>anyone comments otherwise, I shall probably finish polishing that, throw
>comments everywhere, and add a test or two and come back with a complete
>patch.
>  
>
Makes sense to me: please fully explore this idea, thanks.

As a minor, secondary, issue, I'm mildly worried by the possibility that
error messages could become less clear, but probably should really
affect only people trying to enable moving on their own types (which
reminds me the old vague idea of providing a recipe for that)

Paolo.