-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[on-demand] Turn monomorphic_const_eval into a proper query, not just a cache. #41310
Conversation
☔ The latest upstream changes (presumably #41319) made this pull request unmergeable. Please resolve the merge conflicts. |
68204ba
to
6dc21b7
Compare
@bors r+ |
📌 Commit 6dc21b7 has been approved by |
Thanks @eddyb :) |
⌛ Testing commit 6dc21b7 with merge 88792cb... |
💔 Test failed - status-appveyor |
@bors: retry |
…akis [on-demand] Turn monomorphic_const_eval into a proper query, not just a cache. The error definitions and reporting logic, alongside with `eval_length` were moved to `librustc`. Both local and cross-crate constant evaluation is on-demand now, but the latter is only used for `enum` discriminants, to replace the manual insertion into the cache which was done when decoding variants. r? @nikomatsakis
☔ The latest upstream changes (presumably #41357) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r- |
The error definitions and reporting logic, alongside with
eval_length
were moved tolibrustc
.Both local and cross-crate constant evaluation is on-demand now, but the latter is only used for
enum
discriminants, to replace the manual insertion into the cache which was done when decoding variants.r? @nikomatsakis