[Not really OT] Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language.
Guillaume Piolat
guillaume.piolat at gmail.com
Fri Jul 26 14:59:52 UTC 2024
On Friday, 26 July 2024 at 08:43:19 UTC, Paolo Invernizzi wrote:
> On Thursday, 25 July 2024 at 19:36:13 UTC, Timon Gehr wrote:
>
>> I am taking issue with throwing overboard even the aspiration
>> of memory safety. You won't get D widely recognized as a safer
>> language if its ecosystem is actively encouraged to build on
>> careless `@trusted` slapping-on, even on functions where it is
>> completely obvious that they have an unsafe interface.
>
> This!
Not really big on @safe (where is the RoI???? where are the
products that beat the competition by being safe), 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"
More information about the Digitalmars-d
mailing list