On Friday, 29 May 2020 at 04:53:07 UTC, Walter Bright wrote:
The subject says it all.
If you care about memory safety, I recommending adding `safe:`
as the first line in all your project modules, and annotate
individual functions otherwise as necessary. For modules with C
declarations, do as you think best.
For everyone else, carry on as before.
Does this mean there's no longer an interest in making @safe the
default? Or is it only DIP 1028 that's being dropped in favor of
a future new DIP?
@safe seemed to be the way to go. It would be a pitty to discard
the entire thing because of the extern(C) issue, which seemed
addressable within DIP 1028 IMO.
