4 ms·
> So the language is stable, but it ships with an unstable, unfinished standard library? No, it does not. It ships with a stable standard library, but methods
by steveklabnik 10y ago
> So the language is stable, but it ships with an unstable, unfinished standard library?
No, it does not. It ships with a stable standard library, but methods that are unstable are also shown in the docs, so you can see what's happening in upcoming releases. And it links to the issue where you can get involved to help bring the method to stable, if that's important to you.
> I see rust advocates being called out on this _all the time_
Called out on what, specifically?
- jdub 10y agoIf we ignore the unnecessary heat of the comment for a moment, there's an interesting developer experience misunderstanding in there. It may even be enough to just change the wording -- instead of "unstable", "proposed"? (Might sound too tentative.)
- Manishearth 10y agoI like this. Perhaps "Proposed, nightly-only" would be even clearer?
- steveklabnik 10y agoYeah, totally. This would make for a very interesting RFC. (There's also always been a disconnect between naming in this regard; that is, you can only use "unstable" things on the "nightly" build of Rust. And while we try to produce a nightly every night, it doesn't always happen, as these last few weeks have shown. That is changing, at least. But "proposed Rust" sounds stranger than "nightly Rust", so this disconnect might persist even if we decided to change "unstable" to "proposed". Side note: Ember and IIRC Chrome call their nightly versions "canary"...)