mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[tuple_array_conversions]: move from complexity to nursery

Browse Source 
Due to outstanding issues:
* https://github.com/rust-lang/rust-clippy/issues/11082
* https://github.com/rust-lang/rust-clippy/issues/11085
* https://github.com/rust-lang/rust-clippy/issues/11100 (https://github.com/rust-lang/rust-clippy/pull/11105)
* https://github.com/rust-lang/rust-clippy/issues/11124
* https://github.com/rust-lang/rust-clippy/issues/11144
This commit is contained in:
Mingwei Samuel 2023-07-12 15:01:37 -07:00
parent 3be3fb7231
commit 4102a309d7
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
clippy_lints/src/tuple_array_conversions.rs
View File

@ -16,8 +16,8 @@
/// Checks for tuple<=>array conversions that are not done with `.into()`. /// Checks for tuple<=>array conversions that are not done with `.into()`.
/// ///
/// ### Why is this bad? /// ### Why is this bad?
/// It's unnecessary complexity. `.into()` works for tuples<=>arrays at or below 12 elements and /// It may be unnecessary complexity. `.into()` works for converting tuples
/// conveys the intent a lot better, while also leaving less room for hard to spot bugs! /// <=> arrays of up to 12 elements and may convey intent more clearly.
/// ///
/// ### Example /// ### Example
/// ```rust,ignore /// ```rust,ignore
@ -31,7 +31,7 @@
/// ``` /// ```
#[clippy::version = "1.72.0"] #[clippy::version = "1.72.0"]
pub TUPLE_ARRAY_CONVERSIONS, pub TUPLE_ARRAY_CONVERSIONS,
complexity, pedantic,
"checks for tuple<=>array conversions that are not done with `.into()`" "checks for tuple<=>array conversions that are not done with `.into()`"
} }
impl_lint_pass!(TupleArrayConversions => [TUPLE_ARRAY_CONVERSIONS]); impl_lint_pass!(TupleArrayConversions => [TUPLE_ARRAY_CONVERSIONS]);