News for hackers. Stuff that matters.
Re:Comparing k-NN in Rust by ben0x539 on Tuesday June 10, 2014 @06:53PM (#7875756)
.unwrap() is checked, if it goes wrong, it will safely cause task failure and stack unwinding. There won't be any memory unsafety.
Re:Comparing k-NN in Rust by andrewflnr on Wednesday June 11, 2014 @02:52AM (#7876751)
You can't get corruption, but I don't consider a program that violently terminates on unexpected input to be "safe". Just semantics, I guess.
Re:Comparing k-NN in Rust by dbaupp on Wednesday June 11, 2014 @03:26AM (#7876826)
Yeah, saying 'safe' around Rust is generally interpreted as meaning memory safety.