Skip to content

Tracking Issue for RFC 3086: macro metavariable expressions #83527

Open

Description

@nikomatsakis

This is a tracking issue for the RFC "3086" (rust-lang/rfcs#3086).
The feature gate for the issue is #![feature(macro_metavar_expr)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved questions and bugs

Implementation history

Activity

  1. added
    B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.
    T-langRelevant to the language team
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Mar 26, 2021
  2. markbt commented on Mar 27, 2021

    @markbt

    There is a working prototype on the markbt/rust/metavariable_expressions branch. This needs feature gating, and there are a couple of TODOs to resolve, but it's otherwise in reasonable shape. I'm planning to work on it over the coming weeks.

  3. markbt commented on Apr 7, 2021

    @markbt

    Update (2021-04-07)

    I've not yet started work on productionizing the prototype on the markbt/rust/metavariable_expressions branch. I plan to start later this month, free time permitting.

  4. added a commit that references this issue on Apr 12, 2021
  5. markbt commented on May 9, 2021

    @markbt

    Update (2021-05-09)

    I still haven't started on this yet as some stuff came up last month that prevented from having the time to work on it. It's still in my plan to work on it, and hopefully I'll have some time soon.

  6. markbt commented on Jun 29, 2021

    @markbt

    Update (2021-06-29)

    Still no progress, as I haven't had any spare time to work on this project. I'm still planning to work on it, and hopefully will get some time soon.

  7. joshtriplett commented on Jul 7, 2021

    @joshtriplett
    Member

    @markbt If you don't expect to find the bandwidth in the near future, would you potentially be interested in seeking help in the form of another owner for this initiative? If you're still interested in driving this, that's fine, but if you'd like us to switch gears from pinging you to broadcasting that the project could use help, we'd be happy to do that.

  8. markbt commented on Jul 9, 2021

    @markbt

    I'd be happy with any help if there's someone available. I still plan to work on it, but personal stuff is getting in the way at the moment. Sorry about that.

    To recap: I have a working prototype on my branch at https://github.com/markbt/rust/tree/metavariable_expressions . The next steps are to rebase that onto the latest master, and then polish it up so that it's ready for inclusion. Then there's also the doc work to make sure the new feature is documented well. Help with any of this would be appreciated.

  9. c410-f3r commented on Jan 29, 2022

    @c410-f3r
    Contributor

    @markbt Are you still working on this feature? If not, then I can pick up from where you stopped

  10. markbt commented on Jan 29, 2022

    @markbt
  11. c410-f3r commented on Jan 30, 2022

    @c410-f3r
    Contributor

    Thank you @markbt

    I will take a look at the branch and then get in touch if any questions arise

  12. added a commit that references this issue on Mar 14, 2022
  13. 62 remaining items

  14. added a commit that references this issue on Sep 28, 2025
  15. added a commit that references this issue on Sep 28, 2025
  16. added a commit that references this issue on Sep 28, 2025
  17. mwlon commented on Nov 15, 2025

    @mwlon
    Contributor

    Are there any recent updates to this? I would love to see it stabilized.

  18. jhpratt commented on Nov 15, 2025

    @jhpratt
    Member

    @mwlon Someone needs to summarize the status and what's being stabilized. I previously volunteered for this, but I've been busy for so long I've not had the time to do so.

  19. mwlon commented on Nov 15, 2025

    @mwlon
    Contributor

    @jhpratt Do you know how involved that might be? Wondering if it's something a potential first-time contributor like me could hope to accomplish in a day or two.

  20. jhpratt commented on Dec 1, 2025

    @jhpratt
    Member

    @mwlon I would think it's doable! It would primarily be going thru this tracking issue, the RFC, and associated issues to determine what is being stabilized, why certain decisions were made, and essentially provide a high-level overview to the unfamiliar.

    If you have questions, joining Zulip is probably the best bet to get quick answers.

  21. added
    S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.
    on Jan 5, 2026
  22. cosmicexplorer commented on Jan 14, 2026

    @cosmicexplorer

    Which zulip channel?

  23. jhpratt commented on Jan 15, 2026

    @jhpratt
    Member

    T-lang would be most likely to get you helpful info, with WG-macros being a close second (though that's not very active).

  24. added
    A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
    on Jan 16, 2026
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

    A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-macro_metavar_expr`#![feature(macro_metavar_expr)]`S-tracking-design-concernsStatus: There are blocking design concerns.S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.T-langRelevant to the language team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions