Is the order of proc-macro expansion defined?

Open
#578 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
compilers, documentation

Research direction

Start by reviewing the Rust Reference's existing coverage of proc-macro expansion and checking how module processing is described. Determine whether expansion order is defined or intentionally unspecified, then update the relevant reference documentation so the ordering rule or lack of one is explicit.

Written by the indexing model from the issue text.

Description

A-macros

Or is it intentionally left undefined (if so, that should be specified)? Proc-macros can have side-effects. If it is defined, what its it? (In source-sequence, starting from crate root, entire module processed before mod statements, or are mod processed as seen?)

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.