I misspelled. I meant the IDE support is great. I use VSCode, but what makes it good is Rust’s language server (rust-analyzer), which should work in any editor that understands the LSP protocol.
I don’t know if a proper IDE exists for rust, but I’ve never needed it.
Visual Studio Code with rust-analyzer has all the features I would expect from an IDE. I mean, rust-analyzer works together with cargo, so refactoring over file boundaries is not an issue. Visual Studio Code has built-in support for debugging and source control…
That said, I am currently trying to change my workflow to use vim instead of Visual Studio Code, due to my laptop’s small screen size. Rust-analyzer works great in vim too, but I still need to tweak a few things, like how warnings from cargo check are being displayed…
Which IDE do you use?
I misspelled. I meant the IDE support is great. I use VSCode, but what makes it good is Rust’s language server (rust-analyzer), which should work in any editor that understands the LSP protocol.
I don’t know if a proper IDE exists for rust, but I’ve never needed it.
Visual Studio Code with rust-analyzer has all the features I would expect from an IDE. I mean, rust-analyzer works together with cargo, so refactoring over file boundaries is not an issue. Visual Studio Code has built-in support for debugging and source control…
That said, I am currently trying to change my workflow to use vim instead of Visual Studio Code, due to my laptop’s small screen size. Rust-analyzer works great in vim too, but I still need to tweak a few things, like how warnings from
cargo checkare being displayed…I highly recommend the vscode extension
error lensif you wanna change how errors/warnings are displayed.