@system blocks and safer @trusted (ST) functions

[ag0aep6g]

On Monday, 26 July 2021 at 00:50:17 UTC, jfondren wrote:
> That's a much more obviously program-affecting change though, 
> you're changing a function signature. It wouldn't make as 
> compelling an example of someone being surprised that they have 
> to review more than just a @safe function when that only that 
> function is changed.

The point stands: Changes to @safe code can compromise memory 
safety. Bruce claimed we would get "a properly segregated code 
base", and that @safe code would be entirely "machine checkable". 
But reviewers still have to be on the lookout for safety issues, 
even when no @trusted or @system code is touched.