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

Timon Gehr timon.gehr at gmx.ch
Wed Jan 15 02:08:18 UTC 2020

On 14.01.20 15:56, Joseph Rushton Wakeling wrote:
> On Tuesday, 14 January 2020 at 05:23:10 UTC, Arine wrote:
>> That's the thing, D has a GC. If you are now trying to push Rust-like 
>> features into @safe to allow @safe non-gc memory, you are going to be 
>> adding restricting code that would otherwise not have to be to be 
>> @safe with a GC. So the language becomes more restrictive like Rust, 
>> all while losing the benefit of having a GC and not needing to worry 
>> about those restrictions. The DIP that tried to disable dynamic array 
>> resizing is proof of that.
> It's not about what _I'm_ doing.  There are already DIPs and 
> experimental features that extend the reach of what @safe can verify, 
> allowing validation of memory safety for various GC-free (or rather, 
> GC-agnostic) scenarios.

Which features and DIPs are those?

More information about the Digitalmars-d mailing list