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.
This is sad news. I was excited for @safe-by-default, and had
hoped that the issue with extern(C) could be solved without
throwing DIP 1028 away entirely.
I hope that you and Atila do not take the reception of DIP 1028
as a blow against @safe in general, and that you will continue to
look for ways to improve the safety of the D language.
