diff options
| author | bors <bors@rust-lang.org> | 2022-11-28 17:22:36 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-11-28 17:22:36 +0000 |
| commit | 12074808c7a5a2fd9005ed228d9347e9e57f72dd (patch) | |
| tree | ee5a2d3fc59321ec70b8824dd5331b6927b1e04f /src/test/rustdoc-ui/coverage/enum-tuple.rs | |
| parent | c8eba8e4a1f8432135e017fe0ac03320d5166432 (diff) | |
| parent | ab576afc18e0b15167388c1a294587962a94d264 (diff) | |
| download | rust-12074808c7a5a2fd9005ed228d9347e9e57f72dd.tar.gz rust-12074808c7a5a2fd9005ed228d9347e9e57f72dd.zip | |
Auto merge of #9865 - nyurik:allow-mixed, r=xFrednet
Add allow-mixed-uninlined-format-args config
Implement `allow-mixed-uninlined-format-args` config param to change the behavior of the `uninlined_format_args` lint. Now it is a part of `style` per [Zulip chat](https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy/topic/.60uninlined_format_args.60.20category), and won't propose inlining in case of a mixed usage, e.g. `print!("{} {}", var, 1+2)`. If the user sets `allow-mixed-uninlined-format-args` config param to `false`, the lint would behave like it did before -- proposing to inline args even in the mixed case.
---
changelog: [`uninlined_format_args`]: Added a new config `allow-mixed-uninlined-format-args` to allow the lint, if only some arguments can be inlined
[#9865](https://github.com/rust-lang/rust-clippy/pull/9865)
changelog: Moved [`uninlined_format_args`] to `style` (Now warn-by-default)
[#9865](https://github.com/rust-lang/rust-clippy/pull/9865)
Diffstat (limited to 'src/test/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions