Kernel buffer overflow exposes iPhone 11 Pro to radio based attacks

[Paul Backus]

On Wednesday, 9 December 2020 at 20:30:57 UTC, Dukc wrote:
>
> I quess the stance on this is where the fundamental 
> disagreement about C code default `@safe`ty lies. If one 
> considers, even in internal code, that `@safe` and `@trusted` 
> are always declarations that calling it can never corrupt 
> memory unless there's a honest mistake in the implementation, 
> your stance on this is perfectly sound.

The meanings of @safe and @trusted are spelled out in the 
language spec. [1] They are not a matter of opinion.

[1] https://dlang.org/spec/function.html#function-safety

> But as it can also work as a limited down-and-dirty bug-finder,

@safe does not find bugs; it prevents them.