DIP 1028--Make @safe the Default--Formal Assessment

Rivet ri at v.et
Fri May 22 17:51:00 UTC 2020


Perhaps not the ideal solution, but would a compiler flag, e.g. 
--strict-safe, that ensures the compiler errors on un- at trusted 
non-D function prototypes be appropriate? This way, those who do 
work on mission-critical stuff can feel a tad better.


More information about the Digitalmars-d-announce mailing list