-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Move recursion check for zsts back to read site instead of access check site #71751
Conversation
Hm... honestly I am not convinced if that is the right fix long-term. I anyway plan to change However, there is no reason to do this re-work now, and this adds a testcase to make sure I find a good way to handle that when I do my planned changes. So, fine for me. |
Neither am I. I did try to fix it in
|
@@ -0,0 +1,32 @@ | |||
// check-pass |
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.
Are we sure "check" is enough?
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.
Yes, the const prop one occurred during mir optimization of fn new
, which will still happen in check mode, and the static one happened during evaluation of the static's initializer, which also happens in check mode.
r=me with that last question resolved. |
@bors r=RalfJung |
📌 Commit c64c776 has been approved by |
☀️ Test successful - checks-azure |
Reverts #71140 (comment)
Fix #71612
Fix #71709
r? @RalfJung