[Not really OT] Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language.

[Paolo Invernizzi]

On Friday, 26 July 2024 at 14:59:52 UTC, Guillaume Piolat wrote:
> On Friday, 26 July 2024 at 08:43:19 UTC, Paolo Invernizzi wrote:

> Not really big on @safe (where is the RoI???? where are the 
> products that beat the competition by being safe)

https://www.adacore.com/uploads/techPapers/222559-adacore-nvidia-case-study-v5.pdf

>, but when
> currently used @trusted has 2 different semantic meanings:
>
> 1 - @trusted that means "I've audited that the @system function 
> I call are memoy-safe. do not grep this, there is nothing to 
> see"
> 2 - @trusted that means "TODO, this is necessary because I've 
> slapped @safe on top and must go on with productive things. 
> I'll get back later! I should have marked this @system in the 
> first place. I promise i'll get back and fix it!!1"

The second one is safe washing. If we need this as an aid tool 
during development it should not be a mere "comment" on code, but 
something that the compiler can enforce: in Elm for example, that 
we are using as a frontend, the compiler complains if you try to 
build a release versione of the code and you have not removed 
things that should not appear in a release.