rustfmt removes `for<T>`
Open
Nobody has claimed this yet.
I-poor-formatting
P-low
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
fn foo()
where
for<T> T: Clone,
{
}
fn bar<T>()
where
T: for<U> Clone,
{
}
Formatted with rustfmt, it becomes:
fn foo()
where
T: Clone,
{
}
fn bar<T>()
where
T: Clone,
{
}
for<T> isn't valid Rust, but removing it looks wrong. However, feel free to close if you disagree.
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 with the Rust Playground reproducer in the issue and inspect rustfmt's handling of the two where-clause examples. The fix is done when formatting preserves the for<T> binders rather than removing them, with coverage for both shown cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100