Is there any published roadmap for the "reasonable time frame"? The last quotes I saw when searching were ancient and optimistically hoped that Rust will hit 1.0 by the end of this year :-). Is there a goal of reaching 1.0 at some rough time frame or is Rust going for "it will be done when it is done"? I'm not pushing for either, they both have their dis/advantages - but it would be nice to be explicit about it either way.
On Wed, Oct 2, 2013 at 8:10 PM, Alex Crichton <[email protected]> wrote: > It is my understanding that there aren't a whole lot of portions of > the libraries/compiler which are 100% guaranteed to not change from > here on out. There are still fairly large language changes in flight > (dynamically sized types, closure reform, etc.) which could have large > impacts on how the language is used. > > In addition to a the language stabilizing, there's also the factor of > libraries stabilizing. Huon's recent work on adding stability > attributes is a fantastic step in this direction though. As Rust moves > forward, the general strategy for us is to first enforce usage of the > stability attributes to prevent regressions in terms of stability > (stable functions calling unstable ones, etc.). After these safeguards > are in place, the plan is to closely scrutinize the core modules of > libstd. From the inside out, interfaces will be pruned/refactored and > flagged as #[stable]. Once an interface is #[stable], the idea is to > be very reluctant to accept modifications to existing functions, and > functions/modules flagged as such can be thought of as being > "backwards compatible" for the time being at least. > > That being said, I've got a fairly large side project which has been > compiling just fine (without modifications) for nearly a month now > which is truly a record for rust. The rate of change in the language > is far less than it used to be, and library APIs are settling down a > little but, but they're still predominately in flux. As usual, Rust is > not currently in a "backwards compatible" state for nearly its entire > surface area (except for maybe the program "fn main() {}"), but it's > certainly a major goal to achieve this within a reasonable time frame.
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
