Fix extend from assuming a fused iterator.
#150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
☔ The latest upstream changes (presumably #152) made this pull request unmergeable. Please resolve the merge conflicts. |
emilio
reviewed
Jun 7, 2019
|
I updated the comment, but the exact details are quite complex (and dealing with parts of librustc I know little about). |
|
Sure, looks good, thanks! |
emilio
approved these changes
Jun 8, 2019
|
@bors-servo r+ |
|
📌 Commit 1fbaf10 has been approved by |
bors-servo
pushed a commit
that referenced
this pull request
Jun 8, 2019
Fix `extend` from assuming a fused iterator. Iterators may resume after returning None. I think it is generally expected that `extend` should stop on the first None. Fixes #147. Specifically, in rustc, there are some situations where an iterator of Results are collected into a `Result<SmallVec, _>` (such as [here](https://github.com/rust-lang/rust/blob/c1c60d292e2dd2deff7084208274f9a02f750d43/src/librustc/ty/relate.rs#L139-L142) which ends up in [this call to `collect`](https://github.com/rust-lang/rust/blob/c1c60d292e2dd2deff7084208274f9a02f750d43/src/librustc/ty/context.rs#L3002)). The [Result adapter](https://github.com/rust-lang/rust/blob/c1c60d292e2dd2deff7084208274f9a02f750d43/src/libcore/result.rs#L1245-L1258) returns None for the first `Err` in the sequence. However, it is possible for an iterator to have additional elements after the first Err. With this bug, SmallVec was falling through to the slow-path `for` loop, and resuming the iterator grabbing too many elements. I believe this was having some bad interactions with the type interner where the additional elements after the `Err` were getting processed (via a `map()`) and interned when they shouldn't be (or otherwise having some side effects from the `map`). <!-- 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/150) <!-- Reviewable:end -->
|
☀️ Test successful - checks-travis |
Merged
bors-servo
pushed a commit
that referenced
this pull request
Jun 10, 2019
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 -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Iterators may resume after returning None. I think it is generally expected that
extendshould stop on the first None.Fixes #147. Specifically, in rustc, there are some situations where an iterator of Results are collected into a
Result<SmallVec, _>(such as here which ends up in this call tocollect). The Result adapter returns None for the firstErrin the sequence. However, it is possible for an iterator to have additional elements after the first Err. With this bug, SmallVec was falling through to the slow-pathforloop, and resuming the iterator grabbing too many elements. I believe this was having some bad interactions with the type interner where the additional elements after theErrwere getting processed (via amap()) and interned when they shouldn't be (or otherwise having some side effects from themap).This change is