4 ms·

That's a great work and great write-up. I'm happy it finally landed. BTW: Rust team now runs unit tests of packages on crates.io, so each compiler release is v

• kibwen 10y ago
  To elaborate: for a long time (since before 1.0) Rust has had a tool called Crater, which attempts to compile every library on crates.io using two different versions of the compiler, to see if the newer version of the compiler has caused any regressions. What's happened recently is that Crater has been superceded by a new tool, called Cargobomb, which not only compiles public Rust code, but also attempts to run test suites (among other things, see https://github.com/brson/cargobomb/blob/master/README.md https://github.com/brson/cargobomb/blob/master/README.md). What's great about this new approach is that it can find regressions that wouldn't manifest as compilation errors, such as the field reordering changes described in the OP.
  • kbenson 10y ago
    > which not only compiles public Rust code, but also attempts to run test suites Ah, giving CPAN Testers[1] some competition. :) If you haven't already got plans for it (or already done it!), I highly suggest starting an initiative to get lots of donated resources so you can really fill out a testing matrix and make it public[2]. Perl's CPAN a good place to look for what works and what they would do differently (or what they have planned), as they have an amazingly robust module testing ecosystem. 1: http://www.cpantesters.org/ http://www.cpantesters.org/ 2: http://matrix.cpantesters.org/?dist=Path-Tiny+0.104 http://matrix.cpantesters.org/?dist=Path-Tiny+0.104