-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
filter lifetimes in impl Trait #44725
Copy link
Copy link
Closed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: 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.Call 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.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: 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.Call 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.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
currently,
impl Traitusages 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.