Rust

5974 readers

14 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

[email protected]

JetBrains RustRover Is Released and Includes a Free Non-Commercial Option (blog.jetbrains.com)

submitted 4 months ago by [email protected] to c/[email protected]

36 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 4 months ago (1 children)

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.

[–] [email protected] 0 points 4 months ago (1 children)

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

[–] [email protected] 0 points 4 months ago (1 children)

What are you talking about?

[–] [email protected] 0 points 4 months ago (1 children)

What part are you struggling with?
The ripgrep (rg) part, or the cargo expand part?

[–] [email protected] 0 points 4 months ago (1 children)

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?

[–] [email protected] 0 points 4 months ago (2 children)

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.

[–] [email protected] 0 points 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.

[–] [email protected] 0 points 4 months ago (1 children)

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.

[–] [email protected] 0 points 4 months ago* (last edited 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.