Connected to Huly®: V_0.6-23213

What do you think of the idea for making a dedicated tool, or adding an option to v doc, to report the . for public comments that miss them?

A potential benefit is that we could find and fix them all in one PR, then run it on the CI too, to keep the repo clean in that aspect.

Yes, I'm thinking to develop a specific tool/script to check functions documentation e.g. find if description ends with a final dot (+ others checks if possible).

As you said, it could be a potential benefit to check documentation in CI.

@lcheylus I've made cmd/tools/find_doc_comments_with_no_dots.v, and used it to find and fix some of the doc comments in builtin and arrays yesterday.

For v run cmd/tools/find_doc_comments_with_no_dots.v vlib/ it returns:

...
> Processed 1386 .v files, found errors: 1416 , in 9985 `pub` declarations, and 6268 pub comment lines.

i.e. it may be a bit early to add that to the CI, but I can add something like this instead:

v run cmd/tools/find_doc_comments_with_no_dots.v vlib/builtin/ vlib/arrays/ vlib/flag/ vlib/bitfield/

to keep these ones from regressing.
(for those it reports with a 0 exit code and:

> Processed 92 .v files, found errors: 0 , in 1064 `pub` declarations, and 756 pub comment lines.

)