You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lolbinarycat opened this issue
May 31, 2025
· 0 comments
Labels
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.C-bugCategory: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.
warning: unescaped backtick
--> src/lib.rs:5:10
|
5 |#[doc = "`"]| ^
|
= help: the opening or closing backtick of an inline code may be missing
= help: if you meant to use a literal backtick, escape it
change: ` to this: \`note: the lint level is defined here --> src/lib.rs:1:8|1 |#[warn(rustdoc::unescaped_backticks)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
fmease
added
A-lints
Area: Lints (warnings about flaws in source code) such as unused_mut.
and removed
A-diagnostics
Area: Messages for errors, warnings, and lints
labels
May 31, 2025
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.C-bugCategory: This is a bug.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.
Code
Current output
Desired output
Rationale and extra context
No response
Other cases
Rust Version
Anything else?
removing
fn foo
causes the warning to be emitted properly.also works with regular doc comments, and even if the first item is not public.
The text was updated successfully, but these errors were encountered: