Decide what we want about `macro_metavar_expr`
Open
Nobody has claimed this yet.
C-discussion
F-macro_metavar_expr
I-lang-radar
T-lang
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
The author of the stabilization PR for macro_metavar_expr has apparently lost interest in further pursuing it:
We've reopened it for now, but probably it'll need a new PR regardless. To clear the way for that, probably we should decide what it is that we want to see here. Let's use this issue to track our answering of that.
@rustbot labels +T-lang +C-discussion
cc @rust-lang/lang @rust-lang/wg-macros
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading stabilization PR #122808 and the issue discussion to understand the current proposal for macro_metavar_expr. The immediate goal is to decide and document the desired behavior and requirements before a new implementation PR is pursued.
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
- Needs clarification
- Newbie friendliness
- 20/100