this post was submitted on 27 Jun 2024
74 points (88.5% liked)
Rust
6029 readers
3 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
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
testin the file path lower than everything else. Job done.You two bring shame to the programming community.
Just ripgrep cargo expanded output for f**** sake.
What are you talking about?
What part are you struggling with?
The ripgrep (
rg) part, or thecargo expandpart?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?
Not sure how what I write is this confusing to you.
test.testis not necessarily all tests.cargo expandgives you options for correctly and coherently expanding Rust code, and doesn't expand tests by default.rgwas half a joke since it's Rust's grep. You can just pipecargo expand [OPTIONS] [ITEM]output tovim '+set ft=rust' -orbat --filename t.rsand search from there.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.
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.
This type of reductive horseshit has no place anywhere.
"I have a criticism of this piece of software because it does not have this functionality."
"WELL JUST USE A DIFFERENT TOOL!"
Yeah, no shit. This isn't about using a different tool now is it?
You reek of basement-ass teenager that's never actually had to use shit for a living. If you're somehow actually a grown adult I pity your coworkers, who are all likely sick of your garbage-tier attitude.
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 expandoutput anyway. Using that just to avoid searching tests is a super ugly hack.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.