Skip to content

filter lifetimes in impl Trait #44725

Closed
Closed

Description

@nikomatsakis

currently, impl Trait usages capture all lifetimes that are in scope (and this kind of fails around late-bound lifetimes). In the newer RFC, the proposal was that they should only capture those lifetimes that are used in the impl trait itself.

Here are some mentoring instructions I wrote-up from before on how one might do this. But another way to think about this might be to think about implementing abstract type (perhaps in a limited form) and desugaring to that.

However, work on this issue is blocked on #44727.

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Sep 20, 2017
  2. nikomatsakis commented on Sep 20, 2017

    @nikomatsakis
    ContributorAuthor

    See also: #44727

  3. added
    E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
    and removed on Sep 21, 2017
  4. ErichDonGubler commented on Nov 29, 2017

    @ErichDonGubler
    Contributor

    This issue is now ready to be worked on, right? :)

  5. Yoric commented on Dec 1, 2017

    @Yoric
    Contributor

    Since #44727 is closed, I'm interested in working on this. @nikomatsakis a few pointers on which files I'm supposed to dig into would be helpful, though.

  6. nikomatsakis commented on Dec 6, 2017

    @nikomatsakis
    ContributorAuthor

    Er, sorry, this is done actually. =)

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

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCE-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions