Allow Downcast
projections unconditionally in const-checking
#71688
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ProjectionElem::Downcast
sounds scary, but it's really just the projection we use to access a particular enum variant. They usually appear in the lowering of amatch
statement, so they have been associated with control flow in const-checking, but they don't do any control flow by themselves. We already have a HIR pass that looks forif
andmatch
(even ones that have 1 or fewer reachable branches). That pass is double-checked by a MIR pass that looks forSwitchInt
s andFakeRead
s for match scrutinees. In my opinion, there's no need to look forDowncast
as well.r? @oli-obk