Move slice::check_range to RangeBounds#76885
Move slice::check_range to RangeBounds#76885bors merged 4 commits intorust-lang:masterfrom dylni:move-slice-check-range-to-range-bounds
slice::check_range to RangeBounds#76885Conversation
pickfire
left a comment
There was a problem hiding this comment.
Naming for_length looks non-intuitive but the movement looks good.
|
I don't like the name either. What do you think of |
Since this is doing bound checking, how about naming it |
|
|
@rust-highfive missed this PR, so randomly assigning to a libs member. |
|
@dylni I'm not a libs member. |
|
Sorry @joshtriplett. I was looking at this file. r? @KodrAus who reviewed the initial PR. |
|
@dylni Interesting, thanks for pointing me at that. :) |
|
Not a problem. :) It's good to know I'm looking in the right place |
|
📌 Commit f055b0b has been approved by |
|
⌛ Testing commit f055b0b with merge a19dde735bd9a7faeb838e2e786d8b5e884ddff1... |
|
💔 Test failed - checks-actions |
|
@bors retry |
|
@dylni: 🔑 Insufficient privileges: not in try users |
|
@bors retry |
|
⌛ Testing commit f055b0b with merge d04e136f6e752db206b94dfe266a9a5eeeb42424... |
|
💔 Test failed - checks-actions |
|
The failure still doesn't look related to this PR. |
|
@joshtriplett Can you retry bors again? |
@bors retry |
|
☀️ Test successful - checks-actions, checks-azure |
In 1.49 the slice::check_range unstable funciton got moved to RangeBounds::assert_len. rust-lang/rust#76885
Since this method doesn't take a slice anymore (#76662), it makes more sense to define it on
RangeBounds.Questions:
assert_lenorassert_length?