move middle::check_match and middle::const_eval to their own crate #31255
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @arielb1 (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
oli-obk
force-pushed
the
check_match
branch
2 times, most recently
from
8843a5f
to
6f4dc87
Compare
|
@bors r+ |
|
📌 Commit 6f4dc87 has been approved by |
|
🔒 Merge conflict |
|
☔ The latest upstream changes (presumably #31298) made this pull request unmergeable. Please resolve the merge conflicts. |
|
was just a change in error codes right next to one of the moved error codes |
|
let's delay this until after typestrong const ints |
r? @arielb1
this is groundwork for replacing const eval (running on HIR) by a constant propagator (running on MIR)