Rust
Systems programming language and toolchain
Rust's six-week train is spending its budget on soundness, not surface area.
◆Recent moves
- 24d ago
Point release reverts a known LLVM miscompilation trigger
An out-of-band patch that bumps the LLVM submodule for a fix and reverts the rustc change known to trigger the bug. Two of the last four Rust releases have been point releases for codegen or CVE issues, which is the cost of the fast train rather than a sign of instability.
View source ↗ - 1mo ago
v0 symbol mangling becomes the default
⚡ SPARKThe release that changes what Rust binaries look like to everything downstream of the compiler: v0 mangling is now the default, alongside build.warnings and resolver.lockfile-path reaching stable in Cargo. It fits the consolidation arc — a long-planned default finally flipped rather than a new feature added.
View source ↗ - 1mo ago
Cargo libssh2 CVE patches and a MIR miscompilation fix
A security-and-codegen point release: three libssh2 CVEs patched in Cargo plus a MIR optimization miscompilation. Reinforces the pattern where the .1 releases in this window carry security content rather than features.
View source ↗ - 2mo ago
assert_matches! and core::range reach stable
A representative release for this stretch: assert_matches!, the core::range types and several From impls stabilize, two Cargo CVEs are fixed, and the Compatibility Notes tighten Pin coercions and repr(Int) layout. Incremental in every direction, with the corrective work outweighing the additive work.
View source ↗ - 3mo ago
if let guards stabilize; Apple aarch64 targets hit Tier 2
The largest feature batch in the window: if let guards on match arms stabilize, inline assembly lands for PowerPC, and seven aarch64 Apple targets across tvOS, watchOS and visionOS move to Tier 2. The platform promotions are the more consequential half — moving existing targets up-tier is the platform strategy visible across these releases.
View source ↗ - 4mo ago
wasm thread spawn fix and a tar CVE update in Cargo
A small patch release fixing thread::spawn on wasm32-wasip1-threads, withdrawing unstable Windows OpenOptionsExt methods that could not be added compatibly, and updating tar for two CVEs. Notable mainly for the withdrawal, which is the same trait-sealing caution visible in the Compatibility Notes of the larger releases.
View source ↗