Skip to content

Show proc-macro loading errors in unresolved-proc-macro diagnostics #12544

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

Merged
merged 4 commits into from
Jun 15, 2022

Conversation

Veykril
Copy link
Member

@Veykril Veykril commented Jun 15, 2022

This should help out people to potentially figure out the problem without having to check the logs

@Veykril Veykril marked this pull request as draft June 15, 2022 15:40
@Veykril Veykril marked this pull request as ready for review June 15, 2022 16:06
@Veykril
Copy link
Member Author

Veykril commented Jun 15, 2022

@bors r+

@bors
Copy link
Contributor

bors commented Jun 15, 2022

📌 Commit 1dd2c50 has been approved by Veykril

@bors
Copy link
Contributor

bors commented Jun 15, 2022

⌛ Testing commit 1dd2c50 with merge d39d520...

@bors
Copy link
Contributor

bors commented Jun 15, 2022

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing d39d520 to master...

@bors bors merged commit d39d520 into rust-lang:master Jun 15, 2022
@Veykril Veykril deleted the proc-error branch June 15, 2022 16:36
@juchiast
Copy link

juchiast commented Jun 20, 2022

It shows tokio::main as unresolved, should I just disable this diagnostic? Or is this a bug?

@bjorn3
Copy link
Member

bjorn3 commented Jun 20, 2022

What error message does it exactly show? Also are you on an M1 mac? If so you need to use the same architecture (arm64 or x86_64) for both vscode and rustc. Mixing them will cause proc macros to not work as rust-analyzer compiled for one architecture can't dlopen proc macros compiled for another architecture.

@juchiast
Copy link

@bjorn3 I'm on Linux

[rust-analyzer unresolved-proc-macro] proc macro `main` not expanded: proc macro not found [E]

@flodiebold
Copy link
Member

That's #12450

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants