rust-lang / rust-lang/rfcs

Match destructuring in alternations should be generic over types

Open
#525 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

T-lang
Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

#![feature(globs)]

use Char::*;

enum Char {
    A(int),
    B(i32),
    C(char),
}
fn main(){ 
    let a = Char::A(7);

    // This match doesn't work because `x` changes type inside
    // one arm. The compiler should take this and generate an
    // equivalent of the second `match` example.
    match a {
        A(x) | B(x) | C(x) => println!("{}", x),
    }

    // This works because `x` doesn't change type inside an arm.
    match a {
        A(x) => println!("{}", x),
        B(x) => println!("{}", x),
        C(x) => println!("{}", x),
    }

}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the two Rust match examples in the issue and investigate how alternation patterns currently type bindings across variants. Determine the language and compiler changes needed for bindings with differing types, then define the expected behavior and validation cases for equivalent matches.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.