Re: [PATCH v3 1/2] checkpatch.pl: warn about // comments on private Rust items

[Arnaud Lecomte <contact@arnaud-lcm.com>]

Hi everyone !
Is there any update so far ?

Best regards,
Arnaud

On 23/04/2025 12:33, Arnaud Lecomte wrote:
> On 22/04/2025 17:32, Miguel Ojeda wrote:
>
>> On Tue, Apr 22, 2025 at 4:37 PM Arnaud Lecomte 
>> <contact@arnaud-lcm.com> wrote:
>>> As mentioned earlier, we can reduce the score of any heuristic which
>>> could lead to any important false positive.
>>> In my opinion, as long as the heuristic is relevant, we always have the
>>> possibility to diminish the score associated with the heuristic, hence
>>> preventing unnecessary false positives.
>> Definitely (my comment above for this one was just a note, i.e. there
>> may be nothing to change -- I just thought the commit message referred
>> to just checking "Return" and not "Returns", since it said
>> "imperative").
>>
>>> I think that you are definitely more experienced with what's done
>>> commonly in rust code. Let's maybe change this heuristic definition 
>>> with
>>> @ related to types or some other annotation. Do you have some example I
>>> could have a look to come in the next version with a relevant list of @
>>> we can encounter.
>> What does "references" mean in that heuristic? If you mean external
>> links to some URL, then we typically use Markdown for those. The
>> inline ones like `<https://...>`happen in both comments and docs. The
>> `[...]: https://...` ones are way less common in comments I think (I
>> can't find one).
> We should then remove it. I'll wait for other reviewers for their 
> feedback and then send a new version of the patch serie. Thanks :)
>> As for `@`, if you mean the actual character, I grepped for it in Rust
>> files with the /.*@ regex and found just ~13 matches, and all were the
>> emails and disambiguators I mentioned. So I don't think we really use
>> it for "references" (assuming I understand what that means).
>>
>> I guess you already looked in some `rust/kernel/` files -- some of
>> those are really the best examples of how docs and comments should
>> generally be written.
>> Thanks!
>>
>> Cheers,
>> Miguel
>>