Our great sponsors
-
intellij-plugins
Open-source plugins included in the distribution of IntelliJ IDEA Ultimate and other IDEs based on the IntelliJ Platform
-
rust-analyzer
Discontinued A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
That aside, my suggestion is to install either Visual Studio Code with the rust-analyzer extension, or IntelliJ IDEA with the IntelliJ Rust extension, enable inline type hints, and look up the quickest way to summon a popup containing either the function signature or a rustdoc excerpt for the function/method your pointer or text cursor is over.
You can use rust-analyzer in other editors, but those are the ones I know support inline type hints and are officially supported as the primary development targer of their respective plugins.
That aside, my suggestion is to install either Visual Studio Code with the rust-analyzer extension, or IntelliJ IDEA with the IntelliJ Rust extension, enable inline type hints, and look up the quickest way to summon a popup containing either the function signature or a rustdoc excerpt for the function/method your pointer or text cursor is over.
That aside, my suggestion is to install either Visual Studio Code with the rust-analyzer extension, or IntelliJ IDEA with the IntelliJ Rust extension, enable inline type hints, and look up the quickest way to summon a popup containing either the function signature or a rustdoc excerpt for the function/method your pointer or text cursor is over.
Not really. Or maybe much much later when the implementation gets fixed. You get to learn your way around trivial cases but then there's stuff like this https://github.com/rust-lang/rust/issues/54663 where current borrow checker is wrong about what's being borrowed or https://github.com/rust-lang/rust/issues/58052 where you can in theory explain what and how you want your borrow to be but doing so requires you to (in a case where I got into this bug) put a function inside a closure inside a function with a nasty looking type signature on the inside.
This, besides VSCode use https://vscodium.com/ which is essentially the same but without the MSFT telemetry.