On Friday, 29 May 2020 at 12:22:07 UTC, Steven Schveighoffer
wrote:
On 5/29/20 12:53 AM, 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.
Thank you Walter.
I'm sure this was not easy to decide, and is frustrating. It's
unfortunate that the thrust of DIP1028 could not be saved and
we had to throw out the whole thing for the one bad piece.
It's not unfortunate - it's unnecessary. @safe by default is
still a laudable and (seemingly) attainable goal. Why throw out
the entire DIP instead of removing or altering the controversial
aspect?
