Non-techincal brain, is @safe by default good or not?

[Lutger]

On Wednesday, 27 May 2020 at 12:59:12 UTC, aberba wrote:

> Now I hearing @safe by default which reads like the plan has 
> changed and now the direction is going all-in on everything 
> MUST BE SAFE. After reading the DIP, I getting a feeling I'll 
> need to re-think my programming model to make everything safe. 
> Sound in my understanding like most code will break. 
> Communist/Socialist kind of coding.

'everyday programming' in D is almost certainly memory safe, 
except for any c libraries you might use.

It's exactly the proposition of DIP 1028 that such code continues 
to work, except that now the D code is verified for mistakes that 
might cause memory corruption. As it stands, I believe you don't 
really have to change much if anything at all, virtually all code 
will continue to compile and when it doesn't, it's a good thing 
because then you really are doing something dangerous.

You don't really have to change the way you code or re-think your 
programming model unless you write systems code. But if you do, 
then you are likely already aware of the issues.

It seems most people don't like this, as they feel it's deceiving 
that the compiler marks such everyday code as memory safe when it 
frivolously calls into unsafe C code. But that's the controversy 
- you asked about the DIP itself.