rustfmt forcefully moves trailing comments to irrelevant code above (and not idempotent either)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
I sometimes write enums with a comment at the end saying something like "I should add foo in the future". Like
enum MyEnum {
Bar,
// I should add Foo
}
Unfortunately, rustfmt thinks it would be wise to reformat this into
enum MyEnum {
Bar,
// I should add Foo
}
Even worse, when enabling trailing_comma = "Never", I get the non-idempotent output where first it looks like above without the trailing comma, and then gets moved even further up:
enum MyEnum {
Bar // I should add Foo
}
That formatting is very far from my original intention when writing code, and actively hinders readability as one might now ask why the comment should be related to that last enum variant. I think the behaviour should be changed so that rustfmt leaves the trailing comment with an empty newline as it is.
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 enum examples with rustfmt, including trailing_comma = "Never", and compare repeated formatting runs. Trace the formatter behavior responsible for moving the trailing comment; done means the comment remains on its empty line and formatting is idempotent.
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