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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simpler would be just
debug_assert!
. Also, this should print the lo and hi values, so something like:I agree with @petrochenkov that this might not actually be practical, despite the existence of #47504. And the test failure is further evidence of that. The relevant part of the failing stacktrace:
(Why is line 12 repeated? Not sure.)
parse_check_cfg
is very early in the compiler's execution. Have you run any tests locally with this patch applied, e.g. with "x.py tests tests/ui"? That runs a good subset of the test suite.