Move Constructor Syntax

[Timon Gehr]

On 10/14/24 18:14, RazvanN wrote:
> On Monday, 14 October 2024 at 16:03:15 UTC, RazvanN wrote:
> 
>> overload set (__movector). That way, if we have __copyctor, __movector 
>> and __ctor the compiler can reason on which one should be called 
>> depending on the circumstances and thus infinite loops can be avoided.
>>
> 
> That doesn't fix the templated copy/move constructor issue, which the
> new syntax will probably fix.

I think it's too hacky of a fix in general, what you discussed with Manu 
regarding adding base cases seems more promising.