fix: add missing dot to suppress_restriction_lint_in_const

This commit is contained in:
koka 2023-01-29 02:54:26 +09:00
parent e791522d35
commit 25d455bd17
No known key found for this signature in database
GPG Key ID: A5917A40697774CD
2 changed files with 2 additions and 2 deletions

View File

@ -526,7 +526,7 @@ Whether to allow mixed uninlined format args, e.g. `format!("{} {}", a, foo.bar)
### suppress-restriction-lint-in-const ### suppress-restriction-lint-in-const
In same Whether to suppress a restriction lint in constant code. In same
cases the restructured operation might not be unavoidable, as the cases the restructured operation might not be unavoidable, as the
suggested counterparts are unavailable in constant code. This suggested counterparts are unavailable in constant code. This
configuration will cause restriction lints to trigger even configuration will cause restriction lints to trigger even

View File

@ -446,7 +446,7 @@ pub(crate) fn get_configuration_metadata() -> Vec<ClippyConfiguration> {
/// ///
/// Whether to allow mixed uninlined format args, e.g. `format!("{} {}", a, foo.bar)` /// Whether to allow mixed uninlined format args, e.g. `format!("{} {}", a, foo.bar)`
(allow_mixed_uninlined_format_args: bool = true), (allow_mixed_uninlined_format_args: bool = true),
/// Lint: INDEXING_SLICING /// Lint: INDEXING_SLICING.
/// ///
/// Whether to suppress a restriction lint in constant code. In same /// Whether to suppress a restriction lint in constant code. In same
/// cases the restructured operation might not be unavoidable, as the /// cases the restructured operation might not be unavoidable, as the