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

[Rivet via Digitalmars-d-announce]

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