Removing empty type parameter list results in invalid Rust code
Open
Nobody has claimed this yet.
C-bug
I-invalid-code
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
pub fn foo() {
let x: u32 = 100;
if x as i32<> < 0 {
// ...
}
}
gets formatted into
pub fn foo() {
let x: u32 = 100;
if x as i32 < 0 {
// ...
}
}
Compiling playground v0.0.1 (/playground)
error: `<` is interpreted as a start of generic arguments for `i32`, not a comparison
--> src/lib.rs:3:17
|
3 | if x as i32 < 0 {
| -------- ^ --- interpreted as generic arguments
| | |
| | not interpreted as comparison
| help: try comparing the cast value: `(x as i32)`
error: aborting due to previous error
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 and trace how rustfmt handles the empty type-parameter list after the cast. Compare the input and formatted output, then verify that the formatted example compiles and preserves the intended comparison.
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
- 45/100