Re:Confession Of A C/C++ Programmer (2017)
by Ar-Curunir on Monday January 25, 2021 @07:18PM
(#25910783)
Err there are other ways to prove (memory) safety than exhaustive testing, such as better type systems and static analysis (Rust) or better run time checks (any garbage collected language)
Re:Confession Of A C/C++ Programmer (2017)
by extrememota on Wednesday January 27, 2021 @11:48AM
(#25930427)
Memory safety is not the only type of safety though. There are race conditions for example.
Also, even in math, there are enough mistakes in publications (not just typos, but reasoning errors) which hopefully do not affect the eventual results in any fundamental way. The equivalent of safe code in computer science would be equivalent of completely formal proofs in mathematics (like in Coq and similar languages), but probably much more difficult due to existence of temporal conditions.