Restrictions on constants in match patterns should be documented.

Open
#795 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Start by locating the Rust Reference section covering constants in match patterns, then read RFC 1445 for the complete restrictions. Update the reference to describe the magic standard-library types and the PartialEq/Eq and field-eligibility rule without mentioning #[structural_match]; done means the RFC's restrictions are accurately documented.

Written by the indexing model from the issue text.

Description

A-patterns

The restrictions from RFC 1445 are not mentioned anywhere. Given that #[structural_match] is not intended for stabilization, the reference should avoid mentioning it, and instead mention that a type is eligible if and only if either it is a magic standard-library type or derives PartialEq and Eq and all fields are eligible.

Dominant language
Rust
Stars
1.6k
Forks
607
Avg merge
1d 1h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

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.

More from rust-lang/reference

All issues in rust-lang/reference

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.