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 pipecargo expand [OPTIONS] [ITEM]
output tovim '+set ft=rust' -
orbat --filename t.rs
and search from there.
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.