-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Racer searches for crate sources recursively in all package dependencies #831
Comments
Thanks for reporting, but, I think racer doesn't. |
Well I found this while trying to implement #830 and trying to figure out why I'm getting overly extensive list of crates. Turns out, when looking for crate by name, Lines 696 to 698 in cff609a
Cargo.lock without checking Cargo.toml whether this crate is a direct dependency at all (as both global overrides and Cargo.lock contain many more packages then current Rust code can actually access by name).
Then, even if it didn't find in either of those and when it does look at Lines 380 to 388 in cff609a
|
Thanks, I understand. Racer searches For second problem(recursive search for [dependencies.crate-a]
path = "../../crate-a" and [dependencies.crate-b]
path = "../../crate-b" If Edited(2018/04/25): |
This seems related to #757 -- lots of recursion problems in racer. |
Hmm... |
Thank-you! |
Fixed in my branch. |
Closed via #855 |
It seems that Racer tries to find crate source somewhat too hard, traversing not only dependencies from current Cargo.toml or Cargo.lock (which are the only accessible to current Rust code), but also dependencies of these dependencies and so on recursively. Additionally, it looks in global overrides, again, returning any match, no matter whether it's actually defined and so accessible in current crate's Cargo.toml or not.
The text was updated successfully, but these errors were encountered: