Is @safe still a work-in-progress?

[David Gileadi]

On 8/17/18 7:26 AM, H. S. Teoh wrote:
> It will continue to be a problem as long as @safe is implemented via
> blacklisting, because every single time there's a new language feature,
> there's a chance that a loophole is introduced into @safe. And that's
> not counting the combinatorial explosion of existing language features
> that might lead to @safe loopholes, that we simply haven't thought of
> yet.  It's like allowing anyone to enter your house freely except those
> few people whom you've explicitly named. You can't possibly expect *not*
> to get robbed that way.

We should tag bugs like these as #safecracking