Is @safe still a work-in-progress?

[Walter Bright]

On 8/17/2018 11:17 AM, bachmeier wrote:
> This is a good example of D needing to evolve or fizzle out. I don't see 
> evidence that the community has yet figured out how to evolve the language. If 
> it had, these problems would not be around for so many years.

We deprecate features of D all the time. (Remember the D1 => D2 wrenching change?)

The reason @safe cannot be default at the moment it because -dip1000 needs work, 
and nobody is willing to pitch in and review/pull my PRs on it.