Skip to content

Tracking issue for "clarified ADT kinds" (RFC 1506) #35626

@nikomatsakis

Description

@nikomatsakis
Contributor

Tracking issue for rust-lang/rfcs#1506.

Status:

Fully stabilized.

Stabilized by PR #41145:

  • Numeric fields in struct expressions/patterns S { 0: a, 1: b } are not yet stabilized.

Stabilized by PR #36868:

  • Lifted restrictions on tuple structs/variants are stabilized, i.e. S{..} can be used with any structs and empty tuple structs are permitted without feature gate.

Activity

added
B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.
T-langRelevant to the language team
B-unstableBlocker: Implemented in the nightly compiler and unstable.
on Aug 12, 2016
added a commit that references this issue on Aug 13, 2016
nikomatsakis

nikomatsakis commented on Oct 4, 2016

@nikomatsakis
ContributorAuthor

@rfcbot fcp merge

I propose that we stabilize this feature. There are no known blockers or interactions and it is a relatively minor extension to existing syntax. I would very much welcome the ability to use {} more consistently.

rfcbot

rfcbot commented on Oct 4, 2016

@rfcbot
Collaborator

FCP proposed with disposition to merge. Review requested from:

No concerns currently listed.
See this document for info about what commands tagged team members can give me.

rfcbot

rfcbot commented on Oct 13, 2016

@rfcbot
Collaborator

All relevant subteam members have reviewed. No concerns remain.

rfcbot

rfcbot commented on Oct 20, 2016

@rfcbot
Collaborator

It has been one week since all blocks to the FCP were resolved.

added
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
on Oct 21, 2016
nikomatsakis

nikomatsakis commented on Oct 21, 2016

@nikomatsakis
ContributorAuthor

Entering FCP. Honestly I'm not clear for how long. =) Stabilizations still confuse me a bit.

nikomatsakis

nikomatsakis commented on Nov 2, 2016

@nikomatsakis
ContributorAuthor

The release is coming up, and this has not exactly been a controversial topic, so we've decide to make it official and approve this for stabilization.

added a commit that references this issue on Nov 9, 2016

24 remaining items

aturon

aturon commented on Mar 15, 2017

@aturon
Member

cc @petrochenkov @rust-lang/compiler -- anyone want to make a quick stabilization PR that we can backport to 1.17 beta?

nikomatsakis

nikomatsakis commented on Mar 16, 2017

@nikomatsakis
ContributorAuthor

Stabilization is a great place for a first PR. There are directions available on the forge:

https://forge.rust-lang.org/stabilization-guide.html

Marking this as E-easy and E-mentor.

added
E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
on Mar 16, 2017
nikomatsakis

nikomatsakis commented on Mar 16, 2017

@nikomatsakis
ContributorAuthor

Ah, an important question -- has this been documented? If so, we ought to do that first.

steveklabnik

steveklabnik commented on Mar 16, 2017

@steveklabnik
Member

I do not believe so.

added a commit that references this issue on May 25, 2017
d0811c9
est31

est31 commented on Jun 28, 2017

@est31
Member
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

    B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.B-unstableBlocker: Implemented in the nightly compiler and unstable.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.E-mentorCall for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.T-langRelevant to the language teamfinal-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @steveklabnik@eddyb@nikomatsakis@aturon@glaebhoerl

        Issue actions

          Tracking issue for "clarified ADT kinds" (RFC 1506) · Issue #35626 · rust-lang/rust