RepoJournal
Rust

@rust-lang

The Rust language, Cargo, and the standard library

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: Rust Full archive →

The Wire · Showcase

RUST-ANALYZER FIXES DROP SEMANTICS, COMPILER PREPARES FOR PARALLEL IMPORT RESOLUTION

By RepoJournal · Filed · About Rust

Rust-analyzer corrected a critical flaw in how it handles Drop trait implementations, while the compiler begins architectural changes needed for parallelized import resolution.

The rust-analyzer team merged a fix [1] that ensures Drop::drop only executes when explicitly implemented, closing a gap in semantic correctness that would have caused incorrect behavior in production code. Alongside this, rust-analyzer is aggressively optimizing its query system by removing input queries from the macro expansion pipeline [2] and stripping unnecessary clone operations from IDE SSR [3], changes that collectively improve both performance and maintainability heading into the next release cycle.

On the compiler side, rustc is laying groundwork for import resolution parallelization [4] by replacing the borrow counter detection mechanism with an explicit recursion stack for cycle detection, a fundamental shift required before import resolution can be safely threaded. In parallel, the ImproperCTypes lint family continues its multi-part refactor [5], now preventing stack overflows on irregular recursive types while the team works toward a unified, maintainable linting architecture. A redundant dyn-compatibility check has been removed from the trait solver [6], eliminating duplicate work that was already handled downstream.

The ecosystem continues steady churn across crates.io with routine updates to bn-loader, embers-core, clap-help, and bindport [7] [8] [9] [10], while a new svg-renderer crate is now indexed [11].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Merge pull request #22582 from Veykril/lukaswirth/push-myksxrlknmnl rust-lang/rust-analyzer
  2. [2] Merge pull request #22639 from ada4a/unquerygroup-expand_proc_attr_macros rust-lang/rust-analyzer
  3. [3] Merge pull request #22485 from Shourya742/2026-05-29-remove-clone-subtree-from-ide-ssr rust-lang/rust-analyzer
  4. [4] resolve: Explicit Set for detecting resolution cycles ↗ rust-lang/rust
  5. [5] lint ImproperCTypes: refactor linting architecture (part 3) ↗ rust-lang/rust
  6. [6] Auto merge of #158477 - theemathas:del-dyn-compat-check, r=oli-obk rust-lang/rust
  7. [7] Update crate `bn-loader` rust-lang/crates.io-index
  8. [8] Update crate `embers-core` rust-lang/crates.io-index
  9. [9] Update crate `clap-help` rust-lang/crates.io-index
  10. [10] Update crate `bindport` rust-lang/crates.io-index
  11. [11] Create crate `svg-renderer` rust-lang/crates.io-index

Quick answers

What shipped in Rust on June 30, 2026?
Rust-analyzer corrected a critical flaw in how it handles Drop trait implementations, while the compiler begins architectural changes needed for parallelized import resolution. In total, 67 commits, 11 pull requests, and 1 releases landed.
Who contributed to Rust on June 30, 2026?
2 developers shipped this update, including LorrensP-2158466 and niacdoial.
What were the notable Rust updates?
Merge pull request #22582 from Veykril/lukaswirth/push-myksxrlknmnl, Merge pull request #22639 from ada4a/unquerygroup-expand_proc_attr_macros, and Merge pull request #22485 from Shourya742/2026-05-29-remove-clone-subtree-from-ide-ssr.

More from @rust-lang

Daily updates, in your inbox

Follow Rust

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.