Re:Memory Safety in Rust: A Case Study with C
by amluto on Monday February 05, 2018 @11:33AM
(#16309866)
> Your choices are to adapt and avoid undefined behavior, or switch to a better language.
Sadly, a lot of people choose the third choice: write code in what they imagine C to be, fiddle with it until it compiles without warnings and, if they're trying extra hard, passes limited testing with Valgrind. Then they ship it.
Sadly, a lot of people choose the third choice: write code in what they imagine C to be, fiddle with it until it compiles without warnings and, if they're trying extra hard, passes limited testing with Valgrind. Then they ship it.