Re:Rust Priorities after 1.0
by kibwen on Friday April 17, 2015 @01:03AM
(#9392340)
The notion that memory leaks do not constitute memory unsafety has been the party line for a long time, since last year at least (since we can't prevent memory leaks statically: imagine sending something across a channel to a deadlocked thread (remembering that Rust cannot statically prevent deadlocks in general, only data races)). The disruption this week has been due to a stdlib API that made use of a very specific pattern involving a mix of unsafe code, ownership transfer, and destructors. Previously it was believed that this particular unsafe code could not lead to memory unsafety, but that happens to be untrue when memory leakage is thrown into the mix. As a result of this coming to light people will need to reevaluate unsafe code in destructors in a way that had previously not been considered, which is why there's been a general tizzy about it.
[ Parent
| on HN ]
Re:Rust Priorities after 1.0
by andrewchambers on Friday April 17, 2015 @01:12AM
(#9392361)
Thanks for the explanation.