.unwrap() is checked, if it goes wrong, it will safely cause task failure and st... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

ben0x539 on June 10, 2014 | parent | context | favorite | on: Comparing k-NN in Rust

.unwrap() is checked, if it goes wrong, it will safely cause task failure and stack unwinding. There won't be any memory unsafety.

andrewflnr on June 11, 2014 [–]

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.

dbaupp on June 11, 2014 | [–]

Yeah, saying 'safe' around Rust is generally interpreted as meaning memory safety.

Join us for AI Startup School this June 16-17 in San Francisco!
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact