On Tuesday, 17 July 2018 at 07:27:32 UTC, Jacob Carlborg wrote:
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
Can you explain a bit more here? How does having implicit as a
compiler recognized UDA avoid breaking changes as opposed to it
being implemented like @nogc/@safe (how are those implemented
differently anyway?)
Cheers,
- Ali
