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.

  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    5 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
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      5 months ago

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

          • FizzyOrange@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            5 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
              link
              fedilink
              arrow-up
              2
              arrow-down
              2
              ·
              5 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.
                • BB_C@programming.dev
                  link
                  fedilink
                  arrow-up
                  1
                  arrow-down
                  2
                  ·
                  edit-2
                  5 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
                link
                fedilink
                arrow-up
                1
                ·
                5 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
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  5 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.