DIP 1028---Make @safe the Default---Community Review Round 1

Guillaume Piolat first.last at gmail.com
Fri Jan 3 13:03:52 UTC 2020

On Friday, 3 January 2020 at 11:29:47 UTC, Walter Bright wrote:
> On 1/2/2020 9:06 AM, Guillaume Piolat wrote:
>> - Never needed memory-safety, don't see the point, customers 
>> are not crying. Will not need it in the future.
> Buffer overflows (memory unsafety) are consistently at the top 
> of the list of bugs leading to vulnerable software.

I think what will be useful is accepting the change as -preview, 
let us build with it and then see how many actual bugs it catched.

>> - I'll just slap @trusted everywhere and call is a day
> Arguably better to slap @system everywhere.


> That was indeed the idea behind unsafety as the default. But 
> the programming world has changed. We don't have a choice.

Well yes this sounds like the sort of decision that can avoid 
loss of millions in the far future. It's just a bit annoying, no 

More information about the Digitalmars-d mailing list