`for<>` is erased from macro calls
Open
Nobody has claimed this yet.
A-macros
C-bug
P-low
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
Given this input:
a!(for<> A);
a!(for<A> A);
a!(for<A: A> A);
a!(for<A: ?A> A);
rustfmt produces the following output:
a!(A);
a!(A);
a!(A);
a!(A);
Which is incorrect since macros can depend on the for<...>. (playground)
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
Reproduce the four macro-call examples from the issue and compare rustfmt output with the input. Trace the macro-formatting entry point responsible for removing the for<...> tokens, then verify that formatting preserves each form without changing the macro input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100