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

Some rust workspace can not go to definition #11594

Closed
ExpLife0011 opened this issue Mar 1, 2022 · 3 comments
Closed

Some rust workspace can not go to definition #11594

ExpLife0011 opened this issue Mar 1, 2022 · 3 comments
Labels
C-support Category: support questions S-unactionable Issue requires feedback, design decisions or is blocked on other work

Comments

@ExpLife0011
Copy link

There are some rust workspace go to definition not working.
For example https://github.com/project-serum/anchor/blob/master/tests/lockup/programs/registry/src/lib.rs.

@flodiebold
Copy link
Member

This looks like a cargo workspace nested inside another cargo workspace. Did you open the tests/lockup folder as its own VSCode workspace, or add it to the linkedProjects setting? Otherwise rust-analyzer will not discover this automatically.

@flodiebold
Copy link
Member

See #9661.

@flodiebold flodiebold added S-unactionable Issue requires feedback, design decisions or is blocked on other work C-support Category: support questions labels Mar 4, 2022
@ExpLife0011
Copy link
Author

This looks like a cargo workspace nested inside another cargo workspace. Did you open the tests/lockup folder as its own VSCode workspace, or add it to the linkedProjects setting? Otherwise rust-analyzer will not discover this automatically.

Thanks, I tried it and it worked!

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

No branches or pull requests

2 participants