On Tue, 2018-01-23 at 02:22 +1100, Aleksa Sarai wrote:
Finally, one problem with Rust that I ran into when working on the Rust compiler code itself is the high volatility of the language and the code. Things that used to build fine with Rust 1.19 would break with 1.20 and so on. From a distribution maintainer's point of view, this can be very tedious and annoying.
... is not accurate for any project other than the Rust compiler (and the reason for the Rust compiler having this requirement is so that they can use new language features in the compiler itself, not because of stability issues with the language). Any other Rust project must be able to build on 1.x and 1.(x+1) with no changes (and the Rust compiler team tests this quite heavily).
At least for the upgrade to rust 1.23, we needed to hunt a patch for Firefox, because FF 57 did not build otherwise https://build.opensuse.org/package/view_file/openSUSE:Factory/MozillaFi refox/mozilla-rust-1.23.patch?expand=1 With Rust 1.22, FF 57 built 'just fine' - so this just as a counter- example. But then, new warnings/errors in newer compiler versions is not unique to rust: gcc does that too :) (less common in 'minor version releases' though) Cheers Dominique