-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Stop ICE when referring to foreign static values in statics and consts #17973
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon. |
self.visit_foreign_item(item); | ||
} | ||
//I'm not sure if anything else can be in this | ||
//position |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd just remove this comment.
r=me with comment removed. Thanks! |
Could you also be sure to add a test case for this as well? |
Updated. Is the test case ok? |
Thanks! Could you also squash the commits together as well? |
Ok, I think that worked. |
Isn't it already impossible to refer to the value of a |
It is. There is still an error when you do that, it's just more useful than an ICE. E.g. compiling this code:
before:
after:
|
Expand proc-macros in workspace root, not package root Should fix rust-lang/rust-analyzer#17748. The approach is generally not perfect though as rust-project.json projects don't benefit from this (still, nothing changes in that regard)
(I am new to Git and Github so I'm really sorry if I messed up somewhere)