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

Rollup of 6 pull requests #72378

Merged
merged 16 commits into from
May 20, 2020
Merged

Rollup of 6 pull requests #72378

merged 16 commits into from
May 20, 2020

Conversation

Dylan-DPC-zz
Copy link

Successful merges:

Failed merges:

r? @ghost

marmeladema and others added 16 commits May 16, 2020 18:23
…g an error.

This way the hir is "valid" and we can remove one more call to
`opt_node_id_to_hir_id` but an error is still emitted.

This is another partial fix for rust-lang#71104
`fold` is currently implemented via `try_fold`, but implementing it
directly results in slightly less LLVM IR being generated, speeding up
compilation of some benchmarks.

(And likewise for `rfold`.)

The commit adds `fold` implementations to all the iterators that lack
one but do have a `try_fold` implementation. Most of these just call the
`try_fold` implementation directly.
Many default iterator methods use `try_fold` or `fold`, and these ones
can too.
This was supposed to land as part of rust-lang#72227. (I wish `git push` would
abort when you have uncommited changes.)
Suggest fixes and add error recovery for `use foo::self`

Fixes rust-lang#63741.
I have implemented 2 suggestions on how to fix a `use foo::self` import, however I feel like showing them both might be too verbose.

Additionally, I have also implemented error recovery as [menitoned](rust-lang#63741 (comment)) by @comex.

I believe r? @estebank deals with diagnostics.
Make `fold` standalone.

`fold` is currently implemented via `try_fold`, but implementing it
directly results in slightly less LLVM IR being generated, speeding up
compilation of some benchmarks.

r? @cuviper
…static-morse

Continue lowering for unsupported async generator instead of returning an error.

This way the hir is "valid" and we can remove one more call to
`opt_node_id_to_hir_id` but an error is still emitted.

This is another partial fix for rust-lang#71104

r? @eddyb
…king_issue, r=shepmaster

split_inclusive: add tracking issue number (72360)

Adds tracking issue number ( rust-lang#72360 ) to the unstable feature attributes.
…ulacrum

Remove unused dependencies

Remove some unused dependencies found while while working on rust-lang#72342.
…owup, r=Amanieu

Adjust the zero check in `RawVec::grow`.

This was supposed to land as part of rust-lang#72227. (I wish `git push` would
abort when you have uncommited changes.)

r? @Amanieu
@Dylan-DPC-zz
Copy link
Author

@bors r+ rollup=never p=6

@bors
Copy link
Contributor

bors commented May 20, 2020

📌 Commit 51f80b7 has been approved by Dylan-DPC

@bors
Copy link
Contributor

bors commented May 20, 2020

🌲 The tree is currently closed for pull requests below priority 9000, this pull request will be tested once the tree is reopened

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label May 20, 2020
@pietroalbini
Copy link
Member

@bors treeclosed-

@bors
Copy link
Contributor

bors commented May 20, 2020

⌛ Testing commit 51f80b7 with merge 0aa6751...

@bors
Copy link
Contributor

bors commented May 20, 2020

☀️ Test successful - checks-azure
Approved by: Dylan-DPC
Pushing 0aa6751 to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants