Skip to content

Conversation

@birkenfeld
Copy link
Contributor

Resubmit of #38216.

r? @GuillaumeGomez

BTW, instead of closing a PR just because it is old and the team member who offered to fix it up did not have the time to do so, why not ping them instead? (cc @alexcrichton)

for the new SliceIndex trait. Also made the docs of the unchecked versions a bit clearer; they return a reference, not an "unsafe pointer".
@GuillaumeGomez
Copy link
Member

Just reopen the PR and talk about it with the one who closed it. Generally we ask a first time before closing, but it depends on the member.

Copy link
Member

@GuillaumeGomez GuillaumeGomez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few urls missing.

/// index.
///
/// - If given a position, returns a reference to the element at that
/// position or `None` if out of bounds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add None url please?

/// - If given a position, returns a reference to the element at that
/// position or `None` if out of bounds.
/// - If given a range, returns the subslice corresponding to that range,
/// or `None` if out of bounds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add None url please?


/// Returns a mutable reference to the element at the given index.
/// Returns a mutable reference to an element or subslice depending on the
/// type of index (see [`get()`]) or `None` if the index is out of bounds.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add None url please?

@birkenfeld
Copy link
Contributor Author

Did you look at the closed PR? There is a reason why I did not put in the URLs.

@birkenfeld
Copy link
Contributor Author

Just reopen the PR and talk about it with the one who closed it.

That's what I did, no?

@GuillaumeGomez
Copy link
Member

No I mean, the PR that been closed. You created a new one. However, maybe it wasn't possible to just reopen it? Not sure...

@GuillaumeGomez
Copy link
Member

Oh damn you're right. And no, I didn't look at the original PR before you said it. Then it's all good. Sorry for the incovenience.

@bors: r+ rollup

@bors
Copy link
Collaborator

bors commented Jan 18, 2017

📌 Commit 871357a has been approved by GuillaumeGomez

@birkenfeld
Copy link
Contributor Author

Thanks! Sorry if I sounded a bit frustrated ;)

@GuillaumeGomez
Copy link
Member

It's understandable. Just try to speak with people if you have the feeling things aren't moving. There are a lot of PRs and work done but not always publicly.

@alexcrichton alexcrichton removed the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Jan 19, 2017
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Jan 19, 2017
collections: update docs of slice get() and friends Resubmit of rust-lang#38216. r? @GuillaumeGomez BTW, instead of closing a PR just because it is old and the team member who offered to fix it up did not have the time to do so, why not ping them instead? (cc @alexcrichton)
bors added a commit that referenced this pull request Jan 19, 2017
Rollup of 11 pull requests - Successful merges: #38457, #38922, #38970, #39039, #39091, #39115, #39121, #39149, #39150, #39151, #39165 - Failed merges:
@bors bors merged commit 871357a into rust-lang:master Jan 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants