From: Joe Perches <joe@perches.com>
To: Ryan Foster <foster.ryan.r@gmail.com>, linux-kernel@vger.kernel.org
Cc: rust-for-linux@vger.kernel.org, ojeda@kernel.org
Subject: Re: [PATCH] checkpatch: warn on Rust comments with rustdoc links above items
Date: Tue, 13 Jan 2026 12:57:40 -0800 [thread overview]
Message-ID: <bfb5bee02f2e69ce1eb8c526dd4cfb82de326226.camel@perches.com> (raw)
In-Reply-To: <20260113202138.565332-1-foster.ryan.r@gmail.com>
On Tue, 2026-01-13 at 12:21 -0800, Ryan Foster wrote:
> Add a check to emit a warning when a `//` comment containing rustdoc
> link patterns (like [`Foo`]) appears directly above a Rust item
> declaration. This likely indicates the comment should use `///`
> documentation syntax instead.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -3922,6 +3922,26 @@ sub process {
> "Avoid using '.L' prefixed local symbol names for denoting a range of code via 'SYM_*_START/END' annotations; see Documentation/core-api/asm-annotations.rst\n" . $herecurr);
> }
>
> +# check for Rust comments that should likely be doc comments
> +# Warn when a // comment that looks like documentation (contains rustdoc
> +# link patterns like [`Foo`]) appears directly above a Rust item.
> + if ($realfile =~ /\.rs$/ &&
> + $rawline =~ /^\+(\s*)\/\/\s+(.*)$/) {
No objection but maybe $rawline should be something like:
$rawline =~ m{^\+\s*//(?![/!])(.*)} {
my $comment_text = $1;
etc...
> + my $comment_text = $2;
> + # Check if this looks like a doc comment (contains rustdoc link patterns)
> + # and is NOT a special comment like SAFETY:, TODO:, FIXME:, etc.
> + if ($comment_text =~ /\[`[^\]]+`\]/ &&
> + $comment_text !~ /^\s*(?:SAFETY|TODO|FIXME|NOTE|XXX|HACK|BUG|INVARIANT):/) {
[]
> + # Check if next line starts a Rust item
> + my $nextline = $rawlines[$linenr];
> + if (defined($nextline) &&
> + $nextline =~ /^\+\s*(?:pub(?:\s*\([^)]*\))?\s+)?(?:unsafe\s+)?(?:async\s+)?(?:fn|struct|enum|impl|trait|const|static|type|mod|use)\b/) {
> + WARN("RUST_COMMENT_NOT_DOC",
> + "Comment with rustdoc link pattern may need '///' instead of '//'\n" . $herecurr);
[]
Random grep results:
Note: seems to be used as well
What about NB: and INVARIANTS ?
$ git grep -i -P -oh '^\s*\/\/(?![/!])\s*(?:SAFETY|TODO|FIXME|NOTE|XXX|HACK|BUG|INVARIANT|\w+):' -- '*.rs'| sed -r 's/^\s+//' | sort | uniq -c | sort -rn
2081 // SAFETY:
183 // INVARIANT:
42 // TODO:
33 // CAST:
11 // GUARANTEES:
9 // NOTE:
8 // PANIC:
7 // Note:
6 // TIMEOUT:
6 // https:
3 // Type:
3 // TraitItem:
3 // Pat:
3 // OVERFLOW:
3 // Item:
3 // ImplItem:
3 // GUARANTEE:
3 // ForeignItem:
3 // FIXME:
3 // Expr:
3 // Example:
2 // NB:
2 // core:
2 // Author:
1 // u64:
1 // sym:
1 // std:
1 // span:
1 // sizeof:
1 // Reference:
1 // out:
1 // Object:
1 // namely:
1 // INVARIANTS:
1 // in:
1 // FieldMutability:
1 // Chip:
1 // BOUNDS:
1 // 2:
1 // 1:
next prev parent reply other threads:[~2026-01-13 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:21 Ryan Foster
2026-01-13 20:57 ` Joe Perches [this message]
2026-01-13 21:10 ` [PATCH v2] " Ryan Foster
2026-01-13 21:15 ` Joe Perches
2026-01-13 21:40 ` [PATCH 1/2] " Ryan Foster
2026-01-13 22:26 ` [PATCH] " Miguel Ojeda
2026-01-13 22:38 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfb5bee02f2e69ce1eb8c526dd4cfb82de326226.camel@perches.com \
--to=joe@perches.com \
--cc=foster.ryan.r@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®