News for hackers. Stuff that matters.
Re:Announcing Rust 1.20 by jandrese on Thursday August 31, 2017 @04:02PM (#15143418)
I get that all bets are off once an unsafe() block is in play, but in the intended use case it seems like it should be safe.
Re:Announcing Rust 1.20 by kibwen on Thursday August 31, 2017 @04:15PM (#15143524)
You are correct there. Though we can quibble over the definition of "thread safety", concurrent memory safety is a subset of memory safety, which safe Rust enforces (or at least intends to enforce, modulo bugs).