3 ms·
Right, so you basically have to replay nearly the entire history of Rust versions since 1.54 (that’s what, 6 or 7 stages?) to bootstrap. Compare this to Go, whe
by fmajid 5y ago
Right, so you basically have to replay nearly the entire history of Rust versions since 1.54 (that’s what, 6 or 7 stages?) to bootstrap. Compare this to Go, where there is a stable version of Go 1.4 for bootstrapping, and the current Go 1.18 compiles on it, as opposed to only the previous version of Rust in rustc, so 2 stages, or Zig which can be bootstrapped in a single phase, I believe. That is what I call lack of stability.
- kouteiheika 5y ago...and why should I care that it's somewhat more inconvenient to bootstrap the compiler from scratch? No, seriously, why? What I care about is that the code I wrote on Rust 1.0 still compiles on Rust 1.60. And I do still have code from back then (I started writing Rust just before 1.0 hit) and I can confirm that it still compiles. Yes, I know it sucks for all of the distribution maintainers who want to bootstrap every package from scratch, and I do feel for them, but that's a very niche thing to do which the vast majority of people will not do.