4 ms·
This seems rather confusing compared to Go's commitment to stability with their 1.0 release. I can't really tell whether they're freezing the language or not, b
by skybrian 12y ago
This seems rather confusing compared to Go's commitment to stability with their 1.0 release. I can't really tell whether they're freezing the language or not, but it mostly sounds like they aren't.
- steveklabnik 12y ago> I can't really tell whether they're freezing the language or not The TL;DR is, > To put it simply, our responsibility is to ensure that you never dread upgrading Rust. If your code compiles on Rust stable 1.0, it should compile with Rust stable 1.x with a minimum of hassle. The language is not being 'frozen' in the sense of never changing. But it will change in an additive way, so the code you write today will compile tomorrow just fine.
- dbaupp 12y agoTo add to this: > It’s important to be clear about what we mean by stable. We don’t mean that Rust will stop evolving.
- kibwen 12y agoRust's 1.0 promise is analogous to Go's. Code that works will keep working and new features will come with each new release without breaking old code. The only real difference is Rust's time-based "release train" schedule, compared to Go's milestone-based release schedule.
- frowaway001 12y agoSo future releases will only accumulate new features? Because that approach worked so well in ... C++? PHP? JavaScript? Java? C#?
- kibwen 12y agoFuture releases will accumulate new features as they are deemed useful to the goal of a memory-safe zero-overhead systems programming language. Rust is not interested in feature maximalism, so dread not the kitchen sink. For the features that we do add, we value orthogonality and clean integration with the rest of the language.