-
Notifications
You must be signed in to change notification settings - Fork 145
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 using grow
to the same size.
#151
Conversation
@bors-servo r+ |
📌 Commit 3cfc46a has been approved by |
🔒 Merge conflict |
☔ The latest upstream changes (presumably #152) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors-servo r+ Do you need a release after your fixes? Also, thanks for the patch, and sorry I misunderstood #147 initially, I thought that a rustc update was breaking when compiling Thanks for all the fixes, very welcome :) |
📌 Commit b28c6b3 has been approved by |
🔒 Merge conflict |
☔ The latest upstream changes (presumably #150) made this pull request unmergeable. Please resolve the merge conflicts. |
Yea, if you could make a new release, I'd appreciate it. |
@bors-servo r+ |
📌 Commit 4ba0d0f has been approved by |
Fix using `grow` to the same size. Using `grow` on a spilled SmallVec to the current capacity would free the backing storage when it shouldn't. Fixes #148 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-smallvec/151) <!-- Reviewable:end -->
☀️ Test successful - checks-travis |
Publish 0.6.10. This incorporates #144, #152, #150, and #151, which should all be minor version updates according to semver. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-smallvec/153) <!-- Reviewable:end -->
Using
grow
on a spilled SmallVec to the current capacity would free the backing storage when it shouldn't.Fixes #148
This change is