diff options
| author | bors <bors@rust-lang.org> | 2024-06-28 16:37:43 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-06-28 16:37:43 +0000 |
| commit | 2f80536e8353f7fbbfe72725d25a7feada3d2eb3 (patch) | |
| tree | 68b1c9c8246b04e995fc19ce367312bd74c798fa /compiler/rustc_codegen_gcc/example/subslice-patterns-const-eval.rs | |
| parent | 68a799aea9b65e2444fbecfe32217ce7d5a3604f (diff) | |
| parent | 6de87829da801c10db378e28dd1797434383e651 (diff) | |
| download | rust-2f80536e8353f7fbbfe72725d25a7feada3d2eb3.tar.gz rust-2f80536e8353f7fbbfe72725d25a7feada3d2eb3.zip | |
Auto merge of #13002 - notriddle:notriddle/blank-line, r=Manishearth
doc_lazy_continuation: blank comment line for gap This change addresses cases where doc comments are separated by blank lines, comments, or non-doc-comment attributes, like this: ```rust /// - first line // not part of doc comment /// second line ``` Before this commit, Clippy gave a pedantically-correct warning about how you needed to indent the second line. This is unlikely to be what the user intends, and has been described as a "false positive." Since Clippy is warning you about a highly unintuitive behavior [that Rustdoc actually has](https://notriddle.com/rustdoc-html-demo-11/lazy-continuation-bad/test_dingus_2024/constant.D.html), we definitely want it to output *something*, but the suggestion to indent was poor. Fixes #12917 ``` changelog: [`doc_lazy_continuation`]: suggest blank line for likely-unintended lazy continuations ```
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/subslice-patterns-const-eval.rs')
0 files changed, 0 insertions, 0 deletions
