Compiler panic on type inference for impl Generator yielding a reference

I'm getting

error: internal compiler error: librustc/infer/error_reporting/mod.rs:184: ReEmpty
thread 'main' panicked at 'Box', librustc_errors/lib.rs:554:9

when trying to compile

#![feature(generators, generator_trait)]
use std::ops::Generator;
fn example() -> impl Generator {
    || { yield &1 }
}

on rustc 1.29.0-nightly (e5f6498 2018-07-10) - Playground demo.

This seems to happen when I yield a reference type and don't specify the exact type in impl Generator<Yield=&Whatever>.

We don't generate an error message for the ReEmpty region here and panic instead. Here is the message that should be printed with a placeholder:

error[E0700]: hidden type for `impl Trait` captures lifetime that does not appear in bounds
 --> test-region.rs:3:17
  |
3 | fn example() -> impl Generator {
  |                 ^^^^^^^^^^^^^^
  |
  = note: hidden type `[generator@test-region.rs:4:5: 4:20 for<'r> {i32, &'r i32, ()}]` captures BUG[ReEmpty]

Should ReEmpty be allowed for impl Trait? cc @rust-lang/compiler

Why are we capturing ReEmpty here?

@nikomatsakis

There isn't any ReEmpty in the type. There's some scary code which replaces regions with ReEmpty which is closure related. I'm not sure what is going on there, but perhaps generators should be treated the same? cc @nikomatsakis

@Zoxc

@Zoxc Oh, all of that code is for exporting impl Trait concrete types from inference results, which needs to "connect up" lifetimes inside the inferred concrete type with lifetime parameters.

I think the problem is that the yield_ty of the generator ends up being &'ReEmpty u32, because nothing is constraining it to be anything else. I wonder why this isn't occurring with closures.

This doesn't occur with closures because regionck forces the return type of the closure to outlive the closure's call scope, which prevents ReEmpty from being inferred.

I think that the correct way to fix it would be to ~~require all "implicit" projections in impl Trait types to be well-formed.~~ that goes in the wrong direction.

The requirement we want is that that "implicit" impl Generator for [generator type] makes sense.

That requires that the projections in that impl are alive as long as [generator type] is alive (we don't consider that as a "well-formed" requirement, but the "projection outlives" rules assume that). That does not hold if regions in the projections can be inferred to ReEmpty - we need to be checking that.

I think that in closures, CallSite (from the fix to #29793) is serving that rule with lexical lifetimes - not sure what is checking that with NLL.

Note: the version above is fixed by NLL. need to check whether fix is tight.

@arielb1

@arielb1 any ideas on how to check whether the "fix is tight"? Otherwise perhaps this issue can be closed?

Add regression test for rust-lang#52304

Rollup merge of rust-lang#99549 - JohnTitor:issue-52304, r=compiler-e…

Auto merge of rust-lang#99567 - matthiaskrgr:rollup-08hh3r4, r=matthi…

Navigation Menu

Repository navigation

Compiler panic on type inference for impl Generator yielding a reference #52304

2 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Compiler panic on type inference for impl Generator yielding a reference #52304

Description

Activity

Zoxc commented on Aug 1, 2018

arielb1 commented on Aug 4, 2018

Zoxc commented on Aug 6, 2018

eddyb commented on Aug 18, 2018

arielb1 commented on Aug 19, 2018

arielb1 commented on Aug 19, 2018

arielb1 commented on Aug 19, 2018

arielb1 commented on Aug 19, 2018

arielb1 commented on Aug 19, 2018

2 remaining items

arielb1 commented on Aug 19, 2018

rossmacarthur commented on Dec 25, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions