-
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
Don't drop a hir node after lowering #119284
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
Thank you! |
Et joyeux Noël ! |
☔ The latest upstream changes (presumably #119146) made this pull request unmergeable. Please resolve the merge conflicts. |
5ae3ef7
to
d5b2d88
Compare
@bors retry |
Looks like this wasn't picked up by bors correctly. @cjgillot are you ok with the latest commit? This should be reapproved. |
@bors r- |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (d868bc2): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 669.562s -> 669.056s (-0.08%) |
Fixes #119271.
It seems that all hir nodes that get allocated an id must be placed within the hir on pain of ICEs. In #118527 I dropped guards on never patterns since they're not useful, which caused the ICE.