dip1000 and preview in combine to cause extra safety errors
John Colvin
john.loughran.colvin at gmail.com
Thu Jun 9 12:44:00 UTC 2022
On Thursday, 9 June 2022 at 06:53:55 UTC, Walter Bright wrote:
> The point of @safe by default for C declarations was:
>
> 1. so that we would not be deluged with complaints about
> breaking existing code
>
> 2. so people would use it
>
> What people *will* do with C unsafe by default is:
>
> 1. slap `@trusted:` at the beginning and go on their merry way,
> and nothing was accomplished except annoying people
That is their fault and provides a clear warning sign of where to
look to fix the problem and improve safety. grepping for trusted
is the number 1 way to find starting points for memory safety
problems (aside from gdb/asan)
More information about the Digitalmars-d
mailing list