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

aberba karabutaworld at gmail.com
Wed May 27 12:59:12 UTC 2020


So I'm trying to wrap my head around the DIP 1028 thing here. I'm 
aware @live was introduced to give us rust-like safety. That 
seemed cool as long as it was purely opt-in.

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.

Aside issues with how leadership manage communication and stuff, 
is this move, as I understand it, good or not? (both practical 
everyday use and existing code bases). I'm not getting what 
feedback kicked off this move to @safe by default.

Please help me understand.


More information about the Digitalmars-d mailing list