Skip to content
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

Fix off-by-one in String::remove #30677

Merged
merged 1 commit into from
Jan 3, 2016
Merged

Fix off-by-one in String::remove #30677

merged 1 commit into from
Jan 3, 2016

Conversation

diwic
Copy link
Contributor

@diwic diwic commented Jan 2, 2016

Obviously we can't remove the character one past the end of the String. And we can't today either - we'll just panic at char_at() instead - but if we're going to keep that assertion, we should at least have a correct assertion.

Obviously we can't remove the character one past the end of the String. And we can't today either - we'll just panic at char_at() instead - but if we're going to keep that assertion, we should at least have a correct assertion.
@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (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.

@bluss
Copy link
Member

bluss commented Jan 3, 2016

Thank you!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Jan 3, 2016

📌 Commit 8b398ed has been approved by bluss

bors added a commit that referenced this pull request Jan 3, 2016
Obviously we can't remove the character one past the end of the String. And we can't today either - we'll just panic at char_at() instead - but if we're going to keep that assertion, we should at least have a correct assertion.
@bors
Copy link
Contributor

bors commented Jan 3, 2016

⌛ Testing commit 8b398ed with merge 8f11a9e...

@bors bors merged commit 8b398ed into rust-lang:master Jan 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants