-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New 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
First step towards u128
instead of Const
in PatternKind::Range
#51159
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @cramertj (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. |
r? @oli-obk |
cc @varkor |
Ping from triage @oli-obk! This PR needs your review. |
☔ The latest upstream changes (presumably #51884) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from triage! Wow, after a multi-month process, the blocking PR has been merged 🎉 If I understand correctly, this PR should be unblocked now, however it does require a rebase, @pacman82. |
@TimNN Thanks for the ping; I'll hopefully find the time this weekend. |
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.
just a nit.
Would you also be so kind and squash the commits into a single one?
Ping from triage, @pacman82; looks like this is pretty close. |
r=me with the nits addressed. |
@bors r=oli-obk |
📌 Commit 26c05b1 has been approved by |
First step towards `u128` instead of `Const` in `PatternKind::Range` This PR accomplishes two things: * It adds `ty::Ty` to `PatternKind::Range`. The extra type information will make it easier to remove it from the `hi` and `lo` members. * It exchanges `Const` for `u128` in `Constructor::ConstantRange`.
☀️ Test successful - status-appveyor, status-travis |
This PR accomplishes two things:
ty::Ty
toPatternKind::Range
. The extra type information will make it easier to remove it from thehi
andlo
members.Const
foru128
inConstructor::ConstantRange
.