Skip to content

"escaping bound vars in predicate" with associated_type_bounds, HRTB #70292

@comex

Description

@comex
Contributor

Playground link

#![feature(unboxed_closures, associated_type_bounds)]

fn foo<F>(f: F) where
    F: for<'a> FnOnce<(&'a i32,), Output: 'a> {}

fn main() {
    foo(|x: &i32| -> &i32 { x });
}

produces:

error: internal compiler error: src/librustc_typeck/check/mod.rs:692: escaping bound vars in predicate Obligation(predicate=Binder(OutlivesPredicate(_, ReLateBound(DebruijnIndex(1), BrNamed(DefId(0:5 ~ playground[eb44]::foo[0]::'a[0]), 'a)))), depth=0)
 --> src/main.rs:7:5
  |
7 |     foo(|x: &i32| -> &i32 { x }); // OK
  |     ^^^

This does not happen if written out in this form, even though I think it should be equivalent:

    F: for<'a> FnOnce<(&'a i32,)>,
    for<'a> <F as FnOnce<(&'a i32,)>>::Output: 'a,

May or may not be related to #70263.

Activity

changed the title [-]"escaping bound vars in predicate" with unboxed_closures and associated_type_bounds[/-] [+]"escaping bound vars in predicate" with unboxed_closures, associated_type_bounds, HRTB[/+] on Mar 23, 2020
added
C-bugCategory: This is a bug.
I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
requires-nightlyThis issue requires a nightly compiler in some way.
T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
A-associated-itemsArea: Associated items (types, constants & functions)
A-closuresArea: Closures (`|…| { … }`)
on Mar 23, 2020
Centril

Centril commented on Mar 23, 2020

@Centril
Contributor
alexreg

alexreg commented on Mar 23, 2020

@alexreg
Contributor

@Centril Interesting. Is this (should this be) even supported right now? My point is, you can't do this just by concatenating where bounds, so...

Centril

Centril commented on Mar 23, 2020

@Centril
Contributor

Minimized

#![feature(associated_type_bounds)]

fn foo<F>(_: F)
where
    F: for<'a> Trait<Output: 'a>,
{
}

trait Trait {
    type Output;
}

impl<T> Trait for T {
    type Output = ();
}

fn main() {
    foo(());
}

The "desugared" version compiles fine.

changed the title [-]"escaping bound vars in predicate" with unboxed_closures, associated_type_bounds, HRTB[/-] [+]"escaping bound vars in predicate" with associated_type_bounds, HRTB[/+] on Mar 23, 2020
JohnTitor

JohnTitor commented on Oct 7, 2020

@JohnTitor
Member

Triage: This is no longer ICE with the latest nightly, marking as E-needs-test.

added
E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.
on Oct 7, 2020
added a commit that references this issue on Oct 14, 2020
5565241
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-associated-itemsArea: Associated items (types, constants & functions)C-bugCategory: This is a bug.E-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.F-associated_type_bounds`#![feature(associated_type_bounds)]`I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️P-mediumMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.glacierICE tracked in rust-lang/glacier.requires-nightlyThis issue requires a nightly compiler in some way.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @comex@alexreg@Centril@jonas-schievink@JohnTitor

      Issue actions

        "escaping bound vars in predicate" with associated_type_bounds, HRTB · Issue #70292 · rust-lang/rust