diff options
| author | Alejandra González <blyxyas@gmail.com> | 2025-07-29 17:05:13 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-29 17:05:13 +0000 |
| commit | c7dd98c80913b9845f49997142e5bec3524bc343 (patch) | |
| tree | 377d7a09f9380d31814757523aa39ac02ef22b8f /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | b7cc5c45bdf89ea049fc63c41479a1cae265ead5 (diff) | |
| parent | 0920486fa6c0a3c08e23a867b1e6ca6a5563849b (diff) | |
| download | rust-c7dd98c80913b9845f49997142e5bec3524bc343.tar.gz rust-c7dd98c80913b9845f49997142e5bec3524bc343.zip | |
Do not autofix comments containing bare CR (#15175)
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
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions