RustRover, a JetBrains IDE

RustRover 2026.1 is now available. This release brings: -Native cargo-nextest integration -Call Hierarchy for easier navigation in Rust codebases -Easier macro expansion access -ACP Agent Registry support -More flexible module creation

Rust turns 11 today 🦀🎉 A lot has changed since 1.0, but the story is still being written. From the first stable release to today, Rust has grown into a language shaped by curiosity, careful design, and a community that keeps raising the bar for software. What’s on your Rust birthday wish list? 🎁 Tell us in the comments.

Correct answer: D) The Rust Programming Handbook by @FrancescoCiull4 🎉

Rust #QuickThinker 👇 Which Rust book is this cover from?

Check the thread above 👆

@AtreyRachit Ferris is Rust's unofficial mascot 🦀 The debugging part? Look up rubber duck debugging, it's the same idea, but a better animal 😉

@rustrover Who's Ferris and how does it help with debugging?

Rubber duck debugging? We don't do that here. We have Ferris 🦀

@herberticus Thanks! Glad you like it 🙂

This is a fantastic feature!

@obiabo_immanuel Appreciate that! 🧡

@rustrover is the best Rust IDE out there.

@ashutoshrana_20 You should! It's free for non-commercial use btw 🙂

@rustrover I am using vs code but I think I need to try this

In large Rust codebases, 'Find Usages' gives you a list. But a list doesn't tell you how execution flows through trait methods and concrete implementations. Call Hierarchy in RustRover does. Navigate call chains step by step, see exactly how a function gets reached, and understand the path, not just the references. Find more about it here 👇 #trace-call-chains-more-easily" target="_blank" rel="nofollow noopener">jetbrains.com/rust/whatsnew/… #NewInRustRover

@FrancescoCiull4 Thanks Francesco 🙌

@rustrover wow!

@AtreyRachit It really shines in trait-heavy codebases where flat usages just don't tell the whole story. Let us know how it goes 🦀

@rustrover That sounds like a game changer for debugging complex Rust codebases, can't wait to try it out

Next week, Utrecht becomes the Rust capital of the world 🇳🇱 RustWeek brings together 900+ developers, maintainers, and the people shaping the future of Rust. We are so happy to be part of it. See you there? 🦀 #RustWeek2026 2026.rustweek.org

@PavitraGolchha Exactly 🙏 Our semantic highlighting gives it away here: the trait method is highlighted differently from the inherent method.

@rustrover RustRover semantic highlighting saving us even without opening it 🙏

Rust #QuickThinker 👇 What gets printed?

@sinatosk It’s implied above the snippet: trait Greet { fn hello(&self) -> &'static str { "trait" } } Since S overrides it in impl Greet for S, the trait object call prints impl.

@rustrover where's "Greet" trait?

obj has the type &dyn Greet, so obj.hello() is called through the Greet trait object. That means dynamic dispatch: the vtable points to the Greet implementation for the concrete type S. So this prints: impl The inherent method S::hello() is not part of the trait object, so it isn’t called here. Same method name, different lookup path 🦀

Correct answer is B) "impl"

Check the thread above 👆