miniblog.

← Back to all posts
Dec 19, 2015 at 18:00
What proportion of Rust v1.0 code still works on the latest version? Almost all of it, but we have hard data!
Rust regressions 2015 year end report
Rust regressions 2015 year end report
Hi folks. We care about not breaking code and put a fair bit of effort into it: we have policies about acceptable breakage; compile new versions of Rust against downstream code; track regressions (somewhat) carefully on the issue tracker, fixing most of them before they hit stable releases; submit patches to downstream projects when we do break them; report breaking changes in commits and release notes. When you consider that Rust, unlike any other language, publishes new revisions every 6 week...

Related Posts

Feb 9, 2025 at 00:45
I made some changes to a node express project that I haven't touched in almost five years. I was pleasantly surprised that I only needed to update one dependency to get it working again! (It was sqlite3, which is a native dependency using node-gyp.)
Apr 28, 2024 at 23:23
I tried replace Vec with SmallVec in a really hot loop in difftastic, and it's a huge speedup. It almost *halved* the runtime of one of my test files! I've done a lot of performance tuning of difftastic, so it's surprising to see such a big win. https://crates.io/crates/smallvec
Feb 16, 2024 at 16:43
Why do so few CLI tools use colour inside their error messages? For example, rustc uses colour well in the error display, but there's no special styling of the content in backticks. By contrast, markdown website almost always style backtick text differently from prose. E.g. `field` is not specially styled here.
Photo