RustRover Is Released and Includes a Free Non-Commercial Option | The RustRover Blog
blog.jetbrains.com
We’re excited to announce the general availability of RustRover, the powerhouse IDE for Rust developers!

Rust Rover is out of preview and is free for non-commercial use. The only caveat is:

It’s also important to note that if you’re using a non-commercial license, you cannot opt out of the collection of anonymous usage statistics.

  • lad@programming.devEnglish
    7·
    5 months ago

    I use it and it’s okay but man, how long could it take them to separate search results in tests from not in tests.

    Last time I think I found a similar issue for vscode or rust-analyzer, and the devs said it requires a lot of rework and will not be done for a while. Now I can’t find that but maybe it is a task that is harder than it looks. It would’ve been a total killer feature for me, though

    • FizzyOrange@programming.dev
      41·
      4 months ago

      Ugh yeah that’s infuriating on Github search too. Obviously if I’m searching for some identifier I don’t want 10 pages of results in /tests.

      How hard can it be? Just weight anything with test in the file path lower than everything else. Job done.

      • BB_C@programming.dev
        13·
        4 months ago

        You two bring shame to the programming community.
        Just ripgrep cargo expanded output for f**** sake.

            • FizzyOrange@programming.dev
              1·
              4 months ago

              I know what both of those are and how to use them. But they are entirely relevant to the thread. Did you comment in the wrong place?

              • BB_C@programming.dev
                12·
                4 months ago

                Not sure how what I write is this confusing to you.

                • Tests don’t necessarily live in paths containing test.
                • Code in paths containing test is not necessarily all tests.
                • cargo expand gives you options for correctly and coherently expanding Rust code, and doesn’t expand tests by default.
                • rg was half a joke since it’s Rust’s grep. You can just pipe cargo expand [OPTIONS] [ITEM] output to vim '+set ft=rust' - or bat --filename t.rs and search from there.
                • krangled@programming.dev
                  2·
                  4 months ago

                  You’re not smart. You’re not special. Nobody is giving you a medal because you know a workaround to a developer not implementing a feature request after five years, especially when said feature IS ALREADY IMPLEMENTED in a different language in the same IDE.

                  So again, what does your response have to do with how an IDE works? Nothing. It has nothing to do with it, you’re posting purely to jerk yourself off.

                  • BB_C@programming.dev
                    12·
                    4 months ago

                    My post was a showcase of why there is no substitute for knowing your tools properly, and how when you know them properly, you will never have to wait for 5 minutes, let alone 5 years, for anything, because you never used or needed to use an IDE anyway.

                    This applies universally. No minimum smartness or specialness scores required.

                • FizzyOrange@programming.dev
                  1·
                  4 months ago

                  Ok cool but how does that help when I’m searching a non-Rust project via the GitHub web search interface? I don’t know why I’d want to search cargo expand output anyway. Using that just to avoid searching tests is a super ugly hack.

                  • BB_C@programming.dev
                    1·
                    4 months ago

                    how does that help when I’m searching a non-Rust project via the GitHub web search interface

                    Fair.
                    But you are writing a comment under a topic regarding a Rust-flavored IDE, posted to a Rust community. With neither the IDE nor Rust involved, your quoted problem statement is 100% off-topic.