rust-analyzer adds trait object deref diagnostic, ports rustc inference

How much does an IDE change when it stops guessing at trait-object patterns and starts borrowing more of rustc’s own inference machinery? For Rust developers, rust-analyzer’s June 1 changelog said the answer was visible in v0.3.2921.

The headline addition was a new diagnostic, cannot-implicitly-deref-trait-object. The manual says it fires when a pointer to a trait object is implicitly dereferenced by a pattern, which turns a subtle edge case into something the editor can flag before the compiler has to do the same work later. That kind of warning lands in the exact place Rust users feel friction most: not in the abstract rules of the language, but in the moment a pattern looks valid until the type system pushes back.

The update also made MemDocs cheaper to clone, a small phrase with an outsize effect in an IDE that is constantly shuffling snapshots, syntax trees, and background analysis. rust-analyzer’s own release notes framed the change as part of the same steady cleanup that has defined recent weekly drops. The previous release, v0.3.2904 on May 18, 2026, added several diagnostics of its own, including invalid-range-pat-type, non-exhaustive-record-pat, method-call-illegal-sized-bound, fru-in-destructuring-assignment, cannot-be-dereferenced, and explicit-drop-method-use. It also improved incrementality and completion behavior, a sign that the project has been treating polish and performance as a single problem rather than separate tracks.

The newest changelog kept that rhythm going with fixes to completion behavior, including pattern completion field prioritization and filtering for generic reference parameters. Those are the sort of details that decide whether an IDE feels sharp or noisy in daily use. They matter because rust-analyzer is not a niche helper sitting off to the side. Its public documentation says it provides completion and goto definition for editors including VS Code, Emacs, Vim, and Zed, and the project is developed by Ferrous Systems with support from Mozilla, Embark Studios, and freiheit.com.

The bigger signal was the port of block and loop type inference from rustc. rust-analyzer’s internal type inference documentation already describes a system built around type variables and union-find machinery extracted from rustc, so moving more inference logic over is less a cosmetic tweak than a deeper alignment with compiler behavior. The payoff is straightforward: faster editor feedback that tracks compiler truth more closely. In a language where type puzzles can stall a whole editing session, that makes the difference between an IDE that reacts and one that actually understands.