112 wires and counting

$ follow Rust

Keep up with Rust in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-20
stories 79

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

RUST REVERTS DBG! MACRO AFTER REGRESSION CASCADE

By RepoJournal · Filed · About Rust · Composed from the cited sources · methodology

The `dbg!` macro is going back to square one after three separate regressions forced the compiler team to abandon an experimental tearing optimization.

Rust is reverting the `dbg!` macro to its original implementation across all branches [1]. The macro had been modified in rust-lang/rust#149869, but the change triggered a cascade of regressions that proved too costly to fix forward. Two regressions were caught and patched [1], but a third emerged in #155902 with a proposed fix still pending, making a full revert the safer path. This is the second revert on this change; the team already backed it out on beta to protect the 1.95 release. The decision reflects a pragmatic choice: experimental optimizations to core macros need ironclad testing before shipping, and three bites at the apple is enough.

Elsewhere on the compiler desk, a six-PR rollup landed that spans FreeBSD aarch64 support, miri subtree updates, and xray instrumentation for bare-metal targets [2]. The miri subtree was refreshed independently as well [3]. Privacy checking in the compiler got a structural upgrade [4], moving from fixed-point iteration to a queue-based approach that's more efficient when visibility updates propagate. On the stdarch side, intrinsic test generation got cleaner: the team removed manual indentation logic and now pipe generated sources through rustfmt [5][6], simplifying the test generator significantly. These are quiet wins that improve maintainability without user-facing changes.

Quick answers

What shipped in Rust on May 20, 2026?
The `dbg!` macro is going back to square one after three separate regressions forced the compiler team to abandon an experimental tearing optimization. In total, 68 commits and 11 pull requests landed.
Who contributed to Rust on May 20, 2026?
5 developers shipped this update, including cuviper, JonathanBrouwer, RalfJung, Bryanskiy, and davidtwco.
What were the notable Rust updates?
Revert tearing changes to `dbg!`, Rollup of 6 pull requests, and miri subtree update.