Copy Constructor DIP
Jacob Carlborg
doob at me.com
Tue Jul 17 07:27:32 UTC 2018
On Tuesday, 17 July 2018 at 00:04:12 UTC, Andrei Alexandrescu
wrote:
> Then "negative" :o). In brief @implicit follows the same
> implementation as @safe and @nogc/
Why? This is a breaking change. Why not go with an approach that
does not cause any breaking changes, which is just as easy to do?
It also doesn't required any special casing in the parser. This
is how @selector is implemented.
--
/Jacob Carlborg
More information about the Digitalmars-d
mailing list