rust-lang / rust-lang/rust-clippy
`uninlined_format_args` downgraded back to pedantic in 1.89.0 after upgrade in 1.88.0, no corresponding release notes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Summary
The clippy::uninlined_format_args rule was upgraded to style in 1.88.0 as documented in https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-188
It was then re-downgraded back to pedantic in 1.89.0, with no corresponding release notes. https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-189
Due to lack of release notes about the change, I am not sure if this was an intentional re-downgrade in 1.89.0.
Lint Name
uninlined_format_args
Reproducer
$ rustup run 1.89.0 cargo clippy -q --no-deps -- -W help 2>&1 | grep "uninlined-format-args" | head -1
clippy::uninlined-format-args allow using non-inlined variables in `format!` calls
$ rustup run 1.88.0 cargo clippy -q --no-deps -- -W help 2>&1 | grep "uninlined-format-args" | head -1
clippy::uninlined-format-args warn using non-inlined variables in `format!` calls
$ rustup run 1.87.0 cargo clippy -q --no-deps -- -W help 2>&1 | grep "uninlined-format-args" | head -1
clippy::uninlined-format-args allow using non-inlined variables in `format!` calls
Version
1.89.0
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 CHANGELOG.md entries for Rust 1.88 and 1.89, then run the provided rustup and cargo clippy commands to confirm the lint-level difference. Check the relevant project history or discussion to determine whether the 1.89.0 downgrade was intentional; done means the lint behavior and its release notes accurately reflect that decision.
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
- Needs clarification
- Newbie friendliness
- 35/100