Fix "proc macro not expanded" errors #460
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This seems to eliminate "proc macro X not expanded" errors. Seems like we needed to explicitly enable it.
|
Ugh, now I just tried again and I'm seeing the errors still. So still confused. Maybe this doesn't work after all. |
nathansobo
changed the title
|
This isn't the right path, as @as-cii has discovered that this is related to trying to load dynamic libraries in rust-analyzer after it's been code-signed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #428
Based on this conversation, it seems like we may need to explicitly enable procedural macro support when initializing
rust-analyzer. Although it's strange because there's also this PR which claims to enable support by default.It also seems like we need to configure rust-analyzer with
cargo.loadOutDirsFromCheck: true. When I make both of these configuration changes, I think I'm no longer seeing these warnings. But I'm still not totally confident because I thought it was working before I made the out dirs change and then I ended up seeing the errors again.