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.
literal pattern lowering: use the pattern's type instead of the literal's in
const_to_pat
#138992New 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
literal pattern lowering: use the pattern's type instead of the literal's in
const_to_pat
#138992Changes from all commits
0a05677
3779c6b
7a4d4de
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
what's the difference in the repr between this and mentioning the pattern inline that causes this error?
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.
That would be these lines in the literal pattern checking rules. Byte string literal patterns are assigned a slice reference type if the current scrutinee is known to be a slice reference, and otherwise default to the type of the literal (an array reference). Since that link's from the
master
branch, that's also wheretreat_byte_string_as_slice
was assigned. There's no array unsizing logic for named constant patterns (type-checking code here), so it fails to unify&[u8]
with&[u8;3]
. If, hypothetically, that was special-cased, and the pattern was assigned the type&[u8]
rather than the constant's type, then that example would work too (though without the change this PR makes, it'd also have to settreat_byte_string_as_slice
or it'd be missing length checks).