Random thought of the day:
#cpp is about to beat #rust in its own game by becoming the first "quantum memory safe" language.
Depending on whether you observe the binary running (e.g. by running in Fil-C, c++/sys, to a lesser extend with library hardening and sanitizers) or not (e.g. release builds), the binary will either be memory-safe or not.
@thejvmbender Tools are showing up around C and C++ (Fil-C, c++/sys, standard library hardening, sanitizers) that observe the running program and aborts it when it violates memory safety.
These tools have a runtime cost, so they are recommended for debugging, not for production use.
Whether your program is memory-safe or not depends on whether you have a runtime version or a production version.
It's memory-safety state changes based on whether you observe it or not. Sounds quantum to me :-)
Tobias Hunger
Özkan Pakdil