Clarify the usage of "hints" in const_eval.#26683
Conversation
|
r? @huonw (rust_highfive has picked a reviewer for you, use r? to override) |
eefriedman
force-pushed
the
const-eval-hint
branch
2 times, most recently
from
c05e030 to
a745d0c
Compare
|
☔ The latest upstream changes (presumably #26757) made this pull request unmergeable. Please resolve the merge conflicts. |
|
r? @pnkfelix (random person from the compiler subteam) |
There was a problem hiding this comment.
(It took me a little while to convince myself that this ends up being equivalent to the effect we were getting before via the get_substs parameter, but I now believe the tables in the tcx should match even in the case where check::_match::check_pat was passing in a closure that calls fcx.item_substs(), so this should be okay.)
|
@eefriedman I'm basically all in favor of this PR. I've put some feedback up above but you can treat it as an r=me after a rebase. |
eefriedman
force-pushed
the
const-eval-hint
branch
from
a745d0c to
a1b2d40
Compare
The "hint" mechanism is essentially used as a workaround to compute types for expressions which have not yet been type-checked. This commit clarifies that usage, and limits the effects to the places where it is currently necessary. Fixes rust-lang#26210.
eefriedman
force-pushed
the
const-eval-hint
branch
from
a1b2d40 to
6bdfb05
Compare
|
Rebased. |
|
ping @pnkfelix |
|
@bors r+ |
|
📌 Commit 6bdfb05 has been approved by |
The "hint" mechanism is essentially used as a workaround to compute types for expressions which have not yet been type-checked. This commit clarifies that usage, and limits the effects to the places where it is currently necessary. Fixes #26210.
6 participants
The "hint" mechanism is essentially used as a workaround to compute
types for expressions which have not yet been type-checked. This
commit clarifies that usage, and limits the effects to the places
where it is currently necessary.
Fixes #26210.