-
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
impl RangeArgument for RangeInclusive and add appropriate tests #39936
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (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. |
Oops sorry I think I missed this, apologies! Nevertheless looks great, thank you! @bors: r+ |
📌 Commit 4338290 has been approved by |
⌛ Testing commit 4338290 with merge 44f0926... |
💔 Test failed - status-appveyor |
@bors: retry
* network failure
…On Tue, Feb 28, 2017 at 11:30 AM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2158>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39936 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95Ci6c4E7j29wPhzY5ke6Us6YDj-5ks5rhFm7gaJpZM4MFOCg>
.
|
⌛ Testing commit 4338290 with merge 1808b08... |
💔 Test failed - status-appveyor |
@bors: retry
* s3 outage
…On Tue, Feb 28, 2017 at 1:12 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2160>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39936 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95P9ZhWnz5UnNc5fjrxZ7OZnZevqZks5rhHG2gaJpZM4MFOCg>
.
|
⌛ Testing commit 4338290 with merge 91af879... |
💔 Test failed - status-appveyor |
@bors: retry
* network error
…On Tue, Feb 28, 2017 at 1:24 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2162>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39936 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95H10IWu9S3E9p-ZZ-FpYCDVgoca7ks5rhHRTgaJpZM4MFOCg>
.
|
…excrichton impl RangeArgument for RangeInclusive and add appropriate tests Now that `RangeArgument` returns a `Bound`, the impl for `RangeInclusive` is natural to implement and all that's required are tests around it.
☔ The latest upstream changes (presumably #40167) made this pull request unmergeable. Please resolve the merge conflicts. |
Now that
RangeArgument
returns aBound
, the impl forRangeInclusive
is natural to implement and all that's required are tests around it.