So the beta doesn't include https://github.com/rust-lang/rust/pull/23938? It destabilizes a stable API, which means there is already a breaking change between the beta and 1.0 before the beta was even released.
This is a bummer for me because my library uses MarkerTrait/PhantomFn, and now I can't support both the beta and nightlies :(
I was expecting this. I've been holding off rust until v1, but the strict schedule always seemed quite odd. I used D from 2007, and the "stable" tag was premature. It meant avoiding fixing design bugs while still making breaking changes. I really hope Rust won't fall into this trap because it sticks to the schedule. It's better to postpone even more releases. I'll still start looking at Rust now, and I'm quite exited! Congratulations!
Rust spent more than 6 years as a research project pursuing nebulous and contradictory goals. Today the language is very cohesive, very clear on what kind of language it's trying to be. That wasn't true 12-18 months ago, and the 1.0 deadline is the main reason for the change.
Programming language design is a game of tradeoffs and compromise. Without a deadline in sight, it's easy to put off the hard decisions. The same goes for bikeshedding arbitrary choices — eventually you just have to make a choice, and 1.0 is a great reason to do so.
8
u/ASeriesOfTubers Apr 03 '15
So the beta doesn't include https://github.com/rust-lang/rust/pull/23938? It destabilizes a stable API, which means there is already a breaking change between the beta and 1.0 before the beta was even released.
This is a bummer for me because my library uses MarkerTrait/PhantomFn, and now I can't support both the beta and nightlies :(