Skip to content

Rollup of 9 pull requests - #70338

Closed
Centril wants to merge 35 commits into
rust-lang:masterfrom
Centril:rollup-bkch283
Closed

Rollup of 9 pull requests#70338
Centril wants to merge 35 commits into
rust-lang:masterfrom
Centril:rollup-bkch283

Conversation

@Centril

Copy link
Copy Markdown
Contributor

Successful merges:

Failed merges:

r? @ghost

ecstatic-morseand others added 30 commits March 17, 2020 16:09
…vel-doc, r=Dylan-DPC
Add lint when no doc is present at the crate-level
Follow-up of rust-lang#66267.
r? @kinnison
Replace some desc logic in librustc_lint with article_and_desc
r? @eddyb@Centril@matthewjasper
Followup to rust-lang#69674
Blocked on rust-lang#69498
…atthewjasper
Make `needs_drop` less pessimistic on generators
Generators only have non-trivial drop logic when they may store (in upvars or across yields) a type that does.
This prevents generation of some unnecessary MIR in simple generators. There might be some impact on compile times, but this is probably limited in real-world applications.
~~This builds off of rust-lang#69814 since that contains some fixes that are made relevant by *this* PR (see rust-lang#69814 (comment) (this has been merged)
…op-detector, r=RalfJung
Remove const eval loop detector
Now that there is a configurable instruction limit for CTFE (see rust-lang#67260), we can replace the loop detector with something much simpler. See rust-lang#66946 for more discussion about this. Although the instruction limit is nightly-only, the only practical way to reach the default limit uses nightly-only features as well (although CTFE will still execute code using such features inside an array initializer on stable).
This will at the very least require a crater run, since it will result in an error wherever the "long running const eval" warning appeared before. We may need to increase the default for `const_eval_limit` to work around this.
Resolvesrust-lang#54384 cc rust-lang#49980
r? @oli-obk cc @RalfJung
…r=estebank
Fix invalid suggestion on `&mut` iterators yielding `&` references
Fixesrust-lang#69789.
rustc suggested an invalid code when `&` reference from `&mut` iterator is mutated. The compiler knew we're mutating a value behind `&` reference, but as the assignment RHS is from desugaring, it could only see the iterator expression from source and inserted `mut` there.
r? @estebank
…k,wesleywiser
get rid of ConstPropUnsupported; use ZST marker structs instead
This gets rid of yet another machine-specific error variant.
r? @oli-obk
…r=nikomatsakis
Remove `ReClosureBound`
We now substitute external names for regions in the query response.
r? @nikomatsakis
…r=Centril
Account for bad placeholder types in where clauses
Fixrust-lang#70291. Follow up to rust-lang#69148.
@CentrilCentril added the rollup A PR which is a rollup label Mar 23, 2020
@Centril

Copy link
Copy Markdown
ContributorAuthor

@bors r+ p=9 rollup=never

@bors

bors commented Mar 23, 2020

Copy link
Copy Markdown
Collaborator

📌 Commit 58f4f1e has been approved by Centril

@borsbors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Mar 23, 2020
@CentrilCentril closed this Mar 23, 2020
@Centril
Centril deleted the rollup-bkch283 branch March 23, 2020 23:47
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rollupA PR which is a rollupS-waiting-on-borsStatus: 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.

10 participants

@Centril@bors@ecstatic-morse@mark-i-m@tirr-c@RalfJung@GuillaumeGomez@matthewjasper@jonas-schievink@estebank