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
      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
        1
        ·
        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.
        • 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.