Uh oh!
There was an error while loading. Please reload this page.
Constrain all regions in the concrete type for an opaque type - #60449
Conversation
rust-highfive
commented
May 1, 2019
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
19cc7a4 to
d69784eCompareeddyb
commented
May 1, 2019
r? @pnkfelix |
This comment has been minimized.
This comment has been minimized.
d69784e to
4a1c0ceCompareUh oh!
There was an error while loading. Please reload this page.
pnkfelix
commented
May 2, 2019
@bors r+ |
bors
commented
May 2, 2019
📌 Commit 4a1c0cec7b1fd64237de1468ca99f2bad094070d has been approved by |
matthewjasper
commented
May 2, 2019
@bors r- so that I can fix the comment |
4a1c0ce to
d72f4deComparematthewjasper
commented
May 2, 2019
@bors r=pnkfelix |
bors
commented
May 2, 2019
📌 Commit d72f4de has been approved by |
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis@pnkfelixClosesrust-lang#57464Closesrust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis@pnkfelixClosesrust-lang#57464Closesrust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis@pnkfelixClosesrust-lang#57464Closesrust-lang#60127
…r=pnkfelix Constrain all regions in the concrete type for an opaque type `push_outlives_components` skips some regions in a type, notably the signature of a closure is ignored. Most of the time this is OK, but for opaque types the concrete type is used when checking auto-trait bounds in other functions. cc @nikomatsakis@pnkfelixClosesrust-lang#57464Closesrust-lang#60127
Rollup of 9 pull requests Successful merges: - #60429 (Account for paths in incorrect pub qualifier help) - #60449 (Constrain all regions in the concrete type for an opaque type) - #60486 (Place related refactors) - #60513 (Remove -Z borrowck=compare flag) - #60516 (Remove TypeckMir) - #60517 (Reword casting message) - #60520 (Add rustfmt toml) - #60521 (Migrate tidy to rust 2018 edition) - #60527 (Fix async fn lowering ICE with APIT.) Failed merges: r? @ghost
pnkfelix
commented
May 17, 2019
based on a user request, nominating for backport to stable. (I am assuming a backport to beta in time for the beta-to-stable-rollover is simply not feasible at this point in the cycle.) |
matthewjasper
commented
May 18, 2019
I've also nominated #60765 because it's essentially the second part of this fix. |
pnkfelix
commented
Jun 6, 2019
discussed at T-compiler meeting. Approved for backport to stable channel. |
Centril
commented
Jun 11, 2019
Discussed on T-release meeting; declining point release for now based on sum-total of stable-accepted. |
push_outlives_componentsskips some regions in a type, notably the signatureof a closure is ignored. Most of the time this is OK, but for opaque types the
concrete type is used when checking auto-trait bounds in other functions.
cc @nikomatsakis@pnkfelix
Closes#57464
Closes#60127