The fact that Kai had to look up a long standing compiler bug and can't even make a believable "organic" example shows how disingenuous he is, and how little he understands about safety or its goals. Also, he has shit taste when it comes to asthetics.
@LewisCTech@LukasHozda if you don't write the function it's not you who needs to worry about that. Job of the guy who wrote unsafe to make the interface safe. We have the visibility toolas for that e.g. Mutex, Arc, etc
Fil-C intentionally and disingenously conflates Rust's meaning of memory safety (compile time static analysis leading to runtime robustness) with its meaning (GC and runtime safe crash).
Not comparable, the latter you get in many GC langs. Fil-C's innovation is that it can make old C software less radioactive without requiring extensive patching or rewrites.
@antoniosarosi@gtrakGT I swear to god the "AI can do anything don't read anything I swear" bros can't ship anything actual useful, just more wrappers and tools for said AI.
You can't all sell shovels, someone needs to do the digging at some point