DIP 1018--The Copy Constructor--Community Review Round 1

[RazvanN]

On Saturday, 5 January 2019 at 15:00:32 UTC, Boris-Barboris wrote:
> On Saturday, 5 January 2019 at 14:44:12 UTC, RazvanN wrote:
>> This function is called only explicitly, but after this DIP, 
>> it will get called whenever a S instance will be copied. If 
>> you are against this function being a copy constructor, I can 
>> understand that, but C++ is considering it a copy constructor 
>> and for this first iteration, we are too.
>
> Oh... I didn't know C++ went that way, I now understand your 
> reasoning, sorry.
> You're right, I'm against it, but if that's an expected 
> behavior, it's probably for the best.
>
> How do they deal with ambiguity (multiple copy constructors 
> with different argument tuples), just halt with a compiler 
> error?

Yes.