Skip to content

Pattern types #126

Closed
Closed
@oli-obk

Description

@oli-obk

Proposal

I would like to add minimal pattern types (TyKind::Pat(Ty<'tcx>, Pat<'tcx>) for some definition of Pat<'tcx>). I solely want to add integer range patterns and replace the existing rustc_scalar_layout_start/end attributes with them.

A pattern type is a distinct type from its base type. There is no subtyping relation between pattern types themselves or their base type.

This means you could implement different traits for different pattern types with the same base type. Thus, we just forbid implementing any traits for pattern types.

Creating pattern types will only possible via transmute from the base type. In the future this may become possible via pattern matching, but that needs some care in order to not affect stable code.

Converting pattern types to their base type will only be possible via transmute. In the future this will become possible safely via as casts.

Going beyond this simple new type variant requires an additional MCP. Any additional attempts at adding complexity to this feature may be halted by just referring to this MCP's text.

Mentors or Reviewers

If you have a reviewer or mentor in mind for this work, mention then
here. You can put your own name here if you are planning to mentor the
work.

Process

The main points of the Major Change Process are as follows:

  • File an issue describing the proposal.
  • A types team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Types team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    T-typesAdd this label so rfcbot knows to poll the types teamfinished-final-comment-periodThe FCP has finished, action upon the disposition label needs to be takenmajor-changeA major change proposalmajor-change-acceptedAn accepted major change proposalto-announceAnnounce this issue on triage meeting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions