chavacava

Hi @candiduslynx, thank you for reporting the issue.

Hi @scop, thank you for the proposal. PR are welcome.

Hi @s3rj1k thanks for filling the issue. My understanding is that you want no linter warning on comments like ```go /*There is no space between * and T */ ```...

Hi @abemedia, thanks for filling the issue. My understanding of the issue is you ask for `nolint` be part of the default accepted directives (alongside with `go` and `revive`). Is...

Il will try to do a PR on this subject in the next days. My idea is to go ahead with the proposition by @thaJeztah (i.e. replacing the hard coded...

@NikitaSkrynnik, side note on the rule proposal. IMO, enforcing comment min length will not help at all in comment quality. For example, I'm currently working on a code base where...

@NikitaSkrynnik The problem of checking comment quality is still unresolved; mainly because the more fundamental question "What is a high quality comment" is still unanswered. The paper [A decade of...

Hi @hendrywiranto, thanks for the proposal. IMO the use case addressed by the proposed rule is quite niche. I'm not convinced it fits in the `revive`'s intent of being _general_....

I propose to keep the issue open and see if some other users manifest interest in the rule you propose. Thanks again!

Hi @guettli, thanks for filling the issue. IMO it's a matter of _taste_. For example, I prefer ```go strconv.ParseInt(myID, asDecimal, of32bitsSize) ``` We could wait some feedback from other users...