Skip to content
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

Workspaces fail to properly analyze with certain dependencies #6693

Closed
jkelleyrtp opened this issue Dec 2, 2020 · 3 comments
Closed

Workspaces fail to properly analyze with certain dependencies #6693

jkelleyrtp opened this issue Dec 2, 2020 · 3 comments
Labels
S-unactionable Issue requires feedback, design decisions or is blocked on other work

Comments

@jkelleyrtp
Copy link
Contributor

jkelleyrtp commented Dec 2, 2020

I've been trying to find a web-server library that works for a crate in a workspace and can't find anything. It seems that tokio and async_std or the crates themselves (actix, gotham, warp, tide, etc) break all symbol inference when added as a dependency to a crate in a workspace. I have these flags setup:

  "rust-analyzer.procMacro.enable": true,
  "rust-analyzer.cargo.loadOutDirsFromCheck": true,

For now, I'm just building each crate on its own (no workspace), but this does lead to the issue described in the docs:

If each crate had its own target directory, each crate would have to recompile each of the other crates in the workspace to have the artifacts in its own target directory. By sharing one target directory, the crates can avoid unnecessary rebuilding.

I'm scratching my head because I don't know what other debug information I can provide, other than "I don't see any errors highlighted when my crate is in a workspace."

@flodiebold
Copy link
Member

Can you provide an example workspace that reproduces the problem?

@flodiebold flodiebold added the S-unactionable Issue requires feedback, design decisions or is blocked on other work label Dec 15, 2020
@lnicola
Copy link
Member

lnicola commented Jan 17, 2021

@jkelleyrtp are you still having this issue?

@jkelleyrtp
Copy link
Contributor Author

The issue still persists, but I think Rust Analyzer is running into unrecoverable errors from Rustc.

This is the underlying issue:
rust-lang/rust#79946

I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-unactionable Issue requires feedback, design decisions or is blocked on other work
Projects
None yet
Development

No branches or pull requests

3 participants