Uploaded May 2026 | Updated September 2026, 2 weeks ago
What makes an IDE different from a compiler, and why does Rust push that distinction to its limits? This livestream explores what it means for an IDE to truly “understand” Rust code and why features like name resolution, type inference, and macros make that especially challenging.
In this livestream, Vitaly Bragilevsky will meet Lukas from Zed Industries and Vlad from the JetBrains RustRover team. They will discuss the evolution of Rust IDE support, from the early IntelliJ Rust plugin and RLS to modern rust-analyzer and RustRover, and how ideas and contributors have shaped both ecosystems.
Finally, they’ll compare the architectural foundations behind these tools – rust-analyzer’s query-based incremental engine and RustRover’s IntelliJ PSI-based approach. By examining project models, macro expansion, type inference, and trait solving, they’ll explore two different yet converging visions of Rust IDE design and what comes next, including MIR-level analysis and borrow checking directly in the editor.
This livestream is based on the opening talk One Language, Two IDE Engines from RustWeek 2026 2026.rustweek.org/talks/ides
The slides are available here.https://docs.google.com/presentation/d/1bqJe62o65SeiTSzawvVPPiNrNBVt-UjDTRv2WySoX4k/present
What makes an IDE different from a compiler, and why does Rust push that distinction to its limits? This livestream explores what it means for an IDE to truly “understand” Rust code and why features like name resolution, type inference, and macros make that especially challenging.
In this livestream, Vitaly Bragilevsky will meet Lukas from Zed Industries and Vlad from the JetBrains RustRover team. They will discuss the evolution of Rust IDE support, from the early IntelliJ Rust plugin and RLS to modern rust-analyzer and RustRover, and how ideas and contributors have shaped both ecosystems.
Finally, they’ll compare the architectural foundations behind these tools – rust-analyzer’s query-based incremental engine and RustRover’s IntelliJ PSI-based approach. By examining project models, macro expansion, type inference, and trait solving, they’ll explore two different yet converging visions of Rust IDE design and what comes next, including MIR-level analysis and borrow checking directly in the editor.
This livestream is based on the opening talk One Language, Two IDE Engines from RustWeek 2026 2026.rustweek.org/talks/ides
The slides are available here.https://docs.google.com/presentation/d/1bqJe62o65SeiTSzawvVPPiNrNBVt-UjDTRv2WySoX4k/present
