The Wire · Showcase
RUST 1.97.0 LANDS IN CRATES.IO AS COMPILER INFRASTRUCTURE TIGHTENS
By RepoJournal · Filed · About Rust
The Rust compiler shipped its latest minor release overnight, and crates.io has already cut over to it while the core team continues aggressive cleanup work on the AST layer.
Crates.io moved to Rust 1.97.0 [1] as part of routine toolchain maintenance, but the real momentum is in the language infrastructure work happening upstream. The Rust team landed three significant refactoring efforts: lang item collection cleanups [2], removal of redundant AST token fields that shrink node sizes [3], and a Clippy subtree update [4] that brings itertools and lint improvements across the board. The compiler infrastructure is getting leaner while maintaining compatibility. On the crates.io side, the team adopted the new `regex!` macro [5] introduced in regex 1.13, replacing boilerplate `LazyLock<Regex>` patterns with compile-time regex generation. This is the kind of ergonomic win that compounds across the ecosystem. Bootstrap now prints stack traces on panic [7], making it radically easier to debug build failures, and the c-variadic system gained support for 128-bit integers [6]. CDN IP ranges data received routine updates [8].
Action items
- → Update projects to Rust 1.97.0 at next maintenance window rust-lang/rust [plan]
- → Audit codebase for LazyLock<Regex> patterns and migrate to regex! macro rust-lang/crates.io [plan]
- → Monitor cc-rs for clippy warning fixes if using that dependency rust-lang/cc-rs [monitor]
References
- [1] Update Rust to v1.97.0 ↗ rust-lang/crates.io
- [2] Lang item cleanups ↗ rust-lang/rust
- [3] Remove some AST `tokens` fields ↗ rust-lang/rust
- [4] Clippy subtree update ↗ rust-lang/rust
- [5] Use `regex!` macro instead of `LazyLock<Regex>` ↗ rust-lang/crates.io
- [6] Rollup of 7 pull requests ↗ rust-lang/rust
- [7] Print step stack trace when bootstrap panics ↗ rust-lang/rust
- [8] Update CDN IP ranges data rust-lang/crates.io