3 ms·
Rust is quite different to my knowledge. You can mix n match libraries each using a different language version. I don’t know that the art of language changes is
by vlovich123 5y ago
Rust is quite different to my knowledge. You can mix n match libraries each using a different language version. I don’t know that the art of language changes is tiny either as some of these can be mutually incompatible [1]:
> Each project can opt in to an edition other than the default 2015 edition. Editions can contain incompatible changes, such as including a new keyword that conflicts with identifiers in code. However, unless you opt in to those changes, your code will continue to compile even as you upgrade the Rust compiler version you use.
Now granted it’s entirely possible that a given compiler version accidentally broke comparability when building in a different mode - that’s a bug. It’s also possible that this model does have a limit as to how breaking of a change the editions can have (eg probably the ownership model can’t change drastically) which is maybe what you’re trying to say? Certainly if I recall correctly there have been breaking changes in editions.
[1] https://hkalbasi.github.io/mdbook-ra/appendix-05-editions.html https://hkalbasi.github.io/mdbook-ra/appendix-05-editions.ht...
- pjmlp 5y agoThe limit being that the whole program, including all dependent crates need to compiled from source with the same compiler. Other languages, like Java, C, C++, C#, F#…, also embrace binary libraries and multiple implementations. Rust editions currently don't have an answer for such scenarios.
- vlovich123 5y agoTotally different ecosystem that’s built around the concept of building from source. Binary libraries and alternate compiler implementations haven’t been a priority. In fact, multiple compiler implementations generally don’t exist until the language is much older than Rust is now. It’ll happen.
- nchi3 5y ago>The limit being that the whole program, including all dependent crates need to compiled from source with the same compiler. Which isn't really much of a problem given that the ecosystem is built around cargo compiling from source.