Skip to content

Tracking issue for existential types (RFC 2071) #44685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
3 tasks
withoutboats opened this issue Sep 18, 2017 · 4 comments
Closed
3 tasks

Tracking issue for existential types (RFC 2071) #44685

withoutboats opened this issue Sep 18, 2017 · 4 comments
Labels
A-impl-trait Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch. A-trait-system Area: Trait system A-type-system Area: Type system C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.

Comments

@withoutboats
Copy link
Contributor

This is the tracking issue for existential types, a part of rust-lang/rfcs#2071

Blocking stabilization:

  • Implement
  • Document
  • Decide final syntax
@withoutboats withoutboats added A-impl-trait Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch. A-trait-system Area: Trait system A-type-system Area: Type system C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue. labels Sep 18, 2017
@withoutboats withoutboats mentioned this issue Sep 18, 2017
Merged
@nikomatsakis
Copy link
Contributor

I am closing this as a duplicate of #34511

@Tyler-Hardin
Copy link

I don't see a mention of anything like this in the referenced duplicate. It might be good to add it to the todo list there if this is going to be closed as a dup. (I would do it myself, but I barely grasp the RFC, and even then only in the specific context in which it would be useful to me.)

@Ekleog
Copy link

Ekleog commented May 13, 2018

@aturon This tracking issue having been closed in favor of #34511, would it be possible to update the checklist up there with tracking information for this feature, so that it's easy to figure out whether this part of rust-lang/rfcs#2071 has been implemented, is still under debate, is pending stabilisation, etc.? :)

@pnkfelix pnkfelix mentioned this issue May 16, 2019
Closed
@jethrogb
Copy link
Contributor

I think the relevant issue is #63063

@ibraheemdev ibraheemdev mentioned this issue Jan 3, 2021
Open
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-impl-trait Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch. A-trait-system Area: Trait system A-type-system Area: Type system C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-lang Relevant to the language team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nikomatsakis @Ekleog @jethrogb @Tyler-Hardin @withoutboats