3 ms·

I'm glad to hear that -- I've had bad experiences with some other languages moving too fast and breaking things. I understand that's great for people developing

• steveklabnik 10y ago
  Trust me; we hear you. pre rust 1.0 was not pleasant, and it was even my job to keep up with the changes. For more on how this works: https://blog.rust-lang.org/2014/10/30/Stability.html https://blog.rust-lang.org/2014/10/30/Stability.html https://github.com/rust-lang/rfcs/blob/master/text/1122-language-semver.md https://github.com/rust-lang/rfcs/blob/master/text/1122-lang... https://github.com/rust-lang/rfcs/blob/master/text/1105-api-evolution.md https://github.com/rust-lang/rfcs/blob/master/text/1105-api-... These are the RFCs and policies we came up with when cutting 1.0. I haven't read them in a while, but there haven't been any changes. Some of the text and/or examples might be reflective of the time they're written. Oh, and one more thing: we have a tool, "crater", that we run every so often against every open source package in the ecosystem to make sure things don't break. Some of the most popular packages are built on every commit, as well.