-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Please pin a tracking issue for nightly proc macros #12893
Comments
See #12803 (comment) tl;dr next monday, things should start working out-of-the-box for |
All you have to do to fix them in the versioned ABIs is to copy the changes from the sysroot ABI to the 1.64 ABI. You can just follow #12806 for that I think, so closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First and foremost, thank you for making such a generally wonderful tool! I love rust analyzer :)
However, I have been using r-a for probably almost a month and a half now, maybe more, with proc macros not expanding. This is proving difficult as my codebase really relies on proc macros. Its also giving off a bad look for rust to others looking into the language as we use the nightly compiler.
I read all of #12806 and #12803 but its not clear to me if/when things will be fixed. Is there a way that a path forward with checkboxes can be pinned and updated to track progress, or at least an issue we can subscribe to to know when things are fixed on nightly?
Its also not clear to me if there is a workaround in the meantime - I think I read that there wasn't, but some clarification would be appreciated.
Edit: I saw #12805 but I didn't find it very descriptive of a path forward or clear, and the title does not explicitly mention proc macros.
The text was updated successfully, but these errors were encountered: