Direction for @safe/-dip1000

[IGotD-]

On Monday, 14 February 2022 at 15:50:31 UTC, H. S. Teoh wrote:
>
> The problem with @safe as it is implemented today is that it's 
> implemented as a blacklist rather than a whitelist.
>
> Cf. points 2 and 3 (as applied to memory safety) in:
>
> 	http://ranum.com/security/computer_security/editorials/dumb/index.html

I think @safe has done a fundamental error to allow raw pointers. 
In @safe code the memory management should be completely opaque 
similar to C#/Java/whatever, which in turns makes the language 
more simple to work with. Instead D does the opposite and adds 
stuff which makes memory management more complicated.