4 ms·
That method is not yet available in stable Rust, because it's unstable. If you run that example on stable Rust, you'll see error[E0554]: #[feature] may no
by steveklabnik 10y ago
That method is not yet available in stable Rust, because it's unstable.
If you run that example on stable Rust, you'll see
error[E0554]: #[feature] may not be used on the stable release channel
> isn't finished
I wrote about this here: https://news.ycombinator.com/item?id=13277438 https://news.ycombinator.com/item?id=13277438
TL;DR: stuff starts out being added, sits in unstable for a while, then makes it to stable. No software is ever finished. Stability is not the absence of change; stability is the absence of things breaking.
> I'm curious about what "stable" means to rust advocates
You should read the blog post in the parent comment, as it explains, at length.
- lacampbell 10y agoSo the language is stable, but it ships with an unstable, unfinished standard library? I'm sorry, but that's not what 99% of working programmers would consider "stable". You can argue semantics all you want, but I see rust advocates being called out on this all the time. If you keep having to educate people on this, maybe the problem is not us, but your strange definitions of words like "stable"? Btw, my immediate reaction to seeing that very error message was to stop using rust, and think to myself "I'll use it when it's stable". I'm sure I'm not the only one.
- 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"...)
- Manishearth 10y agoDefine "unfinished". You're being deliberately misleading with that word. The Rust stdlib has everything most folks need. There are some things like simd which are currently being actively pushed that are "missing", but even C++ doesn't have "stable" simd, it has compiler extensions in some compilers. Most of the unstable APIs in the stdlib exist independently in the crates.io ecosystem anyway (or their functionality can be replicated with other stdlib apis). The fact that the rust stdlib can still be improved does not make it unfinished (or, if it does, being "unfinished" is not a bad thing). By that argument every language that still pushes out new versions is unfinished. Your definitions of "stable" and "finished" exclude almost all the languages/compilers out there, I highly doubt these are the definitions that 99% of programmers use.
- lacampbell 10y agoDefine "unfinished". You're being deliberately misleading with that word. Oh I made up my own definition for "unfinished". Just like the rust team has for "stable". Give me time and I'll make a blog post explaining what my redefinition means, then I'll spend my time on hacker news and slashdot and reddit "correcting" everyone. Your definitions of "stable" and "finished" exclude almost all the languages/compilers out there, Changing the API of the standard library on minor release versions is stable now. Got it. Fearless concurrency, etc etc.
- steveklabnik 10y ago> Changing the API of the standard library Adding to the API of the standard library, as SemVer specs. Backwards incompatible changes aren't made. (Except for soundness reasons, which happens in extremely rare circumstances, and are made with great care with regards to the upgrade path.)
- detaro 10y agoRust releases follow SemVer, which is not exactly an uncommon standard for those things. Code that works in released version 1.X.Y is supposed to work in all following versions. Are there languages that won't add backwards-compatible features?
- 10y ago