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

rust-analyzer: Expand macro recursively show "Not available" when rust-analyzer.rust.analyzerTargetDir #15841

Closed
loynoir opened this issue Nov 6, 2023 · 1 comment
Labels
C-bug Category: bug

Comments

@loynoir
Copy link

loynoir commented Nov 6, 2023

rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)

0.3.1722-standalone

rustc version: (eg. output of rustc -V)

rustc 1.73.0

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTC, RUSTUP_HOME or CARGO_HOME)

See below

actual

When

        "rust-analyzer.rust.analyzerTargetDir": "/path/to/gittop/build/v2/RA/",
        "rust-analyzer.linkedProjects": [
            "./path/to/foo/Cargo.toml",
            "./path/to/bar/Cargo.toml",
            ...

rust-analyzer: Expand macro recursively show "Not available"

expected

When

        // "rust-analyzer.rust.analyzerTargetDir": "/path/to/gittop/build/v2/RA/",
        "rust-analyzer.linkedProjects": [
            "./path/to/foo/Cargo.toml",
            "./path/to/bar/Cargo.toml",
            ...

rust-analyzer: Expand macro recursively show expanded source

Extra

  • To prevent RA pollute cargo target dir forever

#15057 (comment)

Need to let RA use target dir different from cargo target dir.

To me, make senses even that bug is solved, I prefer to set rust-analyzer.rust.analyzerTargetDir to another dir

@loynoir loynoir added the C-bug Category: bug label Nov 6, 2023
@loynoir
Copy link
Author

loynoir commented Nov 9, 2023

Misleading name.

@loynoir loynoir closed this as completed Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

No branches or pull requests

1 participant