Formatting a line comment inbetween a function parameter and its type results in the type being commented out
Open
Nobody has claimed this yet.
A-comments
C-bug
I-invalid-code
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
Formatting
fn foo(x: //comment here
u32) {}
results in (on playground 1.8.0-nightly (2025-03-22 b48576b4db))
pub fn foo(x: //comment here u32
) {
}
I agree this is a remarkably weird place to put a comment, but it should at least not result in breaking compilation.
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 reported formatting with the Rust snippet on rustfmt or the referenced Rust Playground version. Trace how the formatter handles a line comment between a parameter and its type, then verify that formatting preserves compilable code and does not comment out the type.
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
- Clearly specified
- Newbie friendliness
- 50/100