4 ms·
I'm curious if anyone has experience maintaining (not writing from scratch) pre-existing systems in Rust - now that it's 6 years old (!), what's it like to inte
by toomanyducks 5y ago
I'm curious if anyone has experience maintaining (not writing from scratch) pre-existing systems in Rust - now that it's 6 years old (!), what's it like to interact with in contexts where you aren't building from the ground up?
- Kenji 5y agoI am maintaining part of a popular Rust crate. Working on existing Rust code and modifying it is a pleasure. It's a lot of fun and I wouldn't trade it back for C++ in a million years.
- forgotpwd16 5y agoHow stable Rust is? That is does, and how often if it does, your crate break or becomes (idiomatically) outdated when a new Rust version is released? Can I for example compile with the latest Rust compiler 1,2,..6 year old code?
- nindalf 5y agoYour code will always compile with newer versions of the compiler. It will never break when you upgrade your compiler. (Modulo bugs that are rare and fixed quickly). The 6-year old Rust 1.0 stability guarantee still holds. > Can I for example compile with the latest Rust compiler 1,2,..6 year old code? Yes. There have been some backward incompatible changes, but those are opt-in. So it wouldn't affect you.
- Kenji 5y agoYou usually have a Minimum Supported Rust Version (MSRV). Depending on crate this has to be set higher or lower. Of course you try to support old Rust compilers as long as possible, but you will bump it up once in a while. Rust has become fairly stable now, especially since it's past the 1.0 release so stuff largely remains backwards compatible. You usually see MSRV requiring a compiler younger than 1-2 years, that's what I'm used to seeing.