Opposite of increment-decrement (for non-loop-counter usage) · mgechev/revive#910

(1 Kommentar) (0 Reaktionen) (0 zugewiesene Personen)Go (316 Forks)github user discovery

good first issuerule proposal

Repository-Metriken

Is your feature request related to a problem? Please describe.

The increment-decrement rule is quite opinionated, as many rules are. However, its suggestion is problematic in the sense that e.g.

it's not that common of a practice in my experience to use ++/-- in contexts other than loop counters in Go code, e.g. stdlib
many programming languages don't even have those operators (for example Python, Rust, Swift, Zig)

Describe the solution you'd like

increment-decrement can be disabled like all others, no problem with that, and that does not require a solution.

But for the above reasons, a rule that would do the opposite of increment-decrement for anything but loop counters would be nice to have.

Describe alternatives you've considered

Just disabling increment-decrement, but that won't help with adoption of the += 1 style.

Additional context

N/A.

Research-Richtung: Studiere die bestehende Implementierung der Increment Decrement Regel in revive (wahrscheinlich in rules/increment decrement.go), um das Muster für das Hinzufügen einer neuen Regel zu verstehen. Entwerfe dann eine neue Regel, die die Verwendung von `i += 1` für nicht Schleifenzählervariablen markiert und stattdessen `i++` vorschlägt (oder umgekehrt).
Tech Stack: go
Domain: backendtooling
Issue Type: Funktion
Schwierigkeit: 3
Geschätzte Zeit: 3-5 Tage
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: Go
Einsteigerfreundlichkeit: 65