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

[Paulo Pinto]

On Monday, 6 January 2020 at 13:18:01 UTC, James Blachly wrote:
> On 1/4/20 8:43 PM, NaN wrote:
>> On Thursday, 2 January 2020 at 09:47:48 UTC, Mike Parker wrote:
>> 
>> Has anybody looked at performance considerations since @safe 
>> mandates bounds checking is left on in release mode?
>
> Great question. Presumably we can compile with nobounds for 
> performance sensitive code.
> IMO this is a reasonable trade-off. Rust leaves bounds checking 
> on always, apparently.

Rust, just like most safe systems programming languages provides 
an escape hatch (which requires unsafe), and also does bounds 
checking elision via dataflow analysis.