19 ms·
Congrats to everyone involved (and there sure are a lot of you)! The TL;DR of the alpha is basically this: 1. The concept of a six-week release cycle begins t
by kibwen 12y ago
Congrats to everyone involved (and there sure are a lot of you)!
The TL;DR of the alpha is basically this:
1. The concept of a six-week release cycle begins today, with the first beta coming in March.
2. Breaking changes will basically cease, with the exception of a list of libraries that are still unstable and features that may be tweaked (https://github.com/rust-lang/rust/wiki/Anticipated-breaking-changes-during-1.0-alpha https://github.com/rust-lang/rust/wiki/Anticipated-breaking-...).
3. Given the aforementioned degree of remaining instability, users should still probably stick to the nightly releases in order to help keep their code up to date and weed out bugs in the compiler.
As ever, it deserves to be reiterated that the 1.0 release does not represent the language being "finished" in any way, only that things will stop breaking. The language will continue evolving rapidly after 1.0, and even the 1.0 release will contain several known (and sometimes rather unfortunate) restrictions that will be backwards-compatibly lifted over time.
Post-1.0, I expect there to be a large community outreach to determine which work to prioritize (for example, I foresee a great clamor for making macros more usable). With developer help I intend to publish a blog post before then detailing exactly which deficiencies Rust 1.0 will contain, and the use cases that they currently either prevent or make awkward.
- fallat 12y agoIt is now time to begin looking into Rust.
- xj9 12y agoGood timing too! I have a few projects coming up that could really benefit from the memory safety and performance features rust offers.
- Animats 12y agoFinally! I hadn't used Rust for two weeks, and when I downloaded the nightly last night, code from two weeks ago was breaking. Feature stability will help.
- eterm 12y agoYes, this is a big deal. I tried looking into Rust a couple of months ago, but the speed of change meant that blog posts and tutorials from just weeks before were sometimes completely broken. Getting to 1.0 means that the ecosystem has a chance to grow properly which means "lesser" coders such as myself have a chance to learn and get involved.
- jacquesm 12y agoTutorials should at a minimum be dated and if possible include the version of rust used when making the tutorial.
- eterm 12y agoAnd most are dated and versioned, but a changing API still meant that the corpus was not expanding and knowledge was being lost. Tutorials got out of date so quickly it was hard to get a foothold when trying to learn. The evolution is important and I don't want to seem like I'm saying it shouldn't have been done the way it was, it was very well managed from what I saw from keeping an eye on the project. I am just happy that it will now be stable letting the ecosystem grow and feed off itself.
- steveklabnik 12y agoThe last week has been extra intense. We set the date for alpha around the time we thought we'd be able to ship everything we needed, and we hit those deadlines! But that meant that the past seven days has seen a _lot_ of stuff land.
- vhbit 12y ago> past seven days has seen a _lot_ of stuff land Yep, and for those who has to stay on master it was pretty nasty time - one day you patch a library, another day you're almost revert yesterday's patch.
- Animats 12y ago
- shadowmint 12y ago> Breaking changes will basically cease, with the exception of a list of libraries that are still unstable It's worth noting that this is a significant point; probably 40-50% of the standard library is 'unstable'. You should expect breaking changes often during the alpha. It's just ridiculous to pretend otherwise. I'm not really a fan of these 'artificial deadlines'. There was no reason today had to be the alpha, other than it was previously said that it would be. There's been a lot of great work going into this release, but the standard library is not ready; it's going to under going some major changes over the next few weeks. I don't really see the point in hitting the alpha 1.0 now, with the library in it's current state.
- steveklabnik 12y agoThe 45% number is misleading, because that's a per-item count. The majority of almost every module is stable, just some of the internals haven't been marked as such yet. In addition, the three modules which will see changes have RFCS that are in their final stages, so they will also stabilize soon. The alpha was always about language items, and an initial commitment to some degree of stability. Beta is the release where things are expected to be in their final form.
- deleted 12y ago[deleted]
- shadowmint 12y agoIf the majority of the modules are already stable, why not wait until they are marked as stable, with a more realistic set of #[unstable] in the standard library for the alpha release? Anyone using the alpha now is being smashed with pointless unstable warnings until they add #![allow(unstable)] ...which basically negates the point of having the lint at all. Surely a better approach would be; if 'we have no idea where it's at at the moment', don't tag the api as unstable. Tag things which wont make it into 1.0 as unstable, so people start getting meaningful warnings about using api features that won't make it into 1.0. Seriously, what tangible benefit do 90 warnings about every single api have when you run a compile? Even if that number slowly drops over the coming weeks, it's still going to be entirely meaningless as an indicator of what will or will not be broken once the beta hits; you're also going to be getting a lot of rubbish feedback from people asking for certain apis (which will be stable for 1.0) to be stable, because of warnings that they're unstable; for example std::fmt. ...while anyone using say, std::raw::TraitObject, or say, alloc::heap::allocate, needs to get a heads up now that they needs to say something and get involved if they want those apis to make it into 1.0 Practically speaking, it feels like you need to roll back to 'unstable' and 'experimental' tags, with the lint warning about experimental, and ignoring unstable. ie. 'unstable' <--- Probably in 1.0, not final yet, don't lint these. 'experimental' <---- wont be in 1.0, lint on these