News for hackers. Stuff that matters.
Re:Rust Priorities after 1.0 by dbaupp on Thursday April 16, 2015 @11:59PM (#9392191)
I think you have the wrong impression about the recent changes, e.g. a recent "regression report"[1] found only two regressions between nightly and the original released beta. Furthermore, several changes have been rejected due to being breaking. The team is seriously committed to stability.

[1]: http://internals.rust-lang.org/t/regression-report-beta-2015...

Re:Rust Priorities after 1.0 by andrewchambers on Friday April 17, 2015 @12:10AM (#9392220)
You can be sure if more people used rust, there would be many more detected breakages. The undetected ones are more worrying.

I get that the language is a beta, but be warned. One example I saw - http://internals.rust-lang.org/t/memcpy-is-backwards/1797

Re:Rust Priorities after 1.0 by dbaupp on Friday April 17, 2015 @12:23AM (#9392256)
Breaks during beta that are not detected seem fine to me: people were not using the feature, and the improvement/bug fix could land without issue.

That particular change caused heartache, yes, but it was purposely made before the beta release, exactly because it was breaking.

Re:Rust Priorities after 1.0 by kibwen on Friday April 17, 2015 @12:24AM (#9392258)
The language was not yet in beta when the linked change was made. Using that change to criticize the stability of the beta is disingenuous.
Re:Rust Priorities after 1.0 by andrewchambers on Friday April 17, 2015 @12:38AM (#9392294)
My mistake.

I also just skimmed the issues page and saw people who are contributors discussing whether a memory leak is classified as unsafe behavior and changing api's based on this. It feels like this sort of thing should be put to rest before you declare any sort of stability.

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.
Re:Rust Priorities after 1.0 by andrewchambers on Friday April 17, 2015 @01:12AM (#9392361)
Thanks for the explanation.