@safe inference fundamentally broken

[Andrei Alexandrescu via Digitalmars-d]

On 6/5/14, 8:30 PM, Timon Gehr wrote:
> The fundamental issue seems to lie in methodology and it is that @safe
> is approximated by the DMD implementation from the wrong side. Instead
> of gradually banning usage of more and more constructs in @safe, the
> implementation should have started out with not allowing any constructs
> in @safe code and then should have gradually allowed more and more
> manually verified to be memory safe constructs.

Agreed. -- Andrei