When a bare CR is present in a four slashes comment, keep triggering the lint but do not issue a fix suggestion as bare CRs are not supported in doc comments. An extra note is added to the diagnostic to warn the user about it. I have put the test in a separate file to make it clear that the bare CR is not a formatting error. Fixes rust-lang/rust-clippy#15174 changelog: [`four_forward_slashes`]: warn about bare CR in comment, and do not propose invalid autofix |
||
|---|---|---|
| .. | ||
| test_utils | ||
| ui | ||
| ui-cargo | ||
| ui-internal | ||
| ui-toml | ||
| workspace_test | ||
| check-fmt.rs | ||
| clippy.toml | ||
| compile-test.rs | ||
| config-metadata.rs | ||
| dogfood.rs | ||
| integration.rs | ||
| lint_message_convention.rs | ||
| missing-test-files.rs | ||
| symbols-used.rs | ||
| versioncheck.rs | ||
| workspace.rs | ||