diff options
| author | bors <bors@rust-lang.org> | 2023-12-13 17:53:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-12-13 17:53:59 +0000 |
| commit | 1839b79e518a9ebc87b82698662f4926adeb6be9 (patch) | |
| tree | c0847461613fb13b37d639cf70bb92816444c173 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | c19508b356c67eb188504fc41692220cc760508e (diff) | |
| parent | 1f2ca8127cf74392d57a1e2526295427134e62f9 (diff) | |
| download | rust-1839b79e518a9ebc87b82698662f4926adeb6be9.tar.gz rust-1839b79e518a9ebc87b82698662f4926adeb6be9.zip | |
Auto merge of #11956 - intgr:doc_markdown-include-function-parenthesis, r=Alexendoo
[`doc_markdown`] Recognize words followed by empty parentheses `()` for quoting *Please write a short comment explaining your change (or "none" for internal only changes)* changelog: [`doc_markdown`] Recognize words followed by empty parentheses for quoting, e.g. `func()`. --- Developers often write function/method names with trailing `()`, but `doc_markdown` lint did not consider that. Old clippy suggestion was not very good: ```patch -/// There is no try (do() or do_not()). +/// There is no try (do() or `do_not`()). ``` New behavior recognizes function names such as `do()` even they contain no `_`/`::`; and backticks are suggested outside of the `()`: ```patch -/// There is no try (do() or do_not()). +/// There is no try (`do()` or `do_not()`). ```
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
