-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Trying to shrink_to greater than capacity should be no-op #81335
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (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. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
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.
r=me with comment restored and commits squashed
@rustbot label -S-waiting-on-author +S-waiting-on-review |
@bors r+ rollup=never |
📌 Commit d069c58 has been approved by |
@bors retry |
☀️ Test successful - checks-actions |
Per the discussion in #56431,
shrink_to
shouldn't panic if you try to make a vector shrink to a capacity greater than its current capacity.