manual-strict-comparison

Prefer strict comparison over offsetting an operand by one

An inclusive integer comparison with an operand offset by one expresses strict ordering through extra arithmetic.
Instead, you SHOULD compare the original operands with < or >.

The rewritten comparison does not preserve an overflow trap produced by the offset at an integer boundary.

- Category: style
- Level: warning
- Fix: suggestion
- Scope: module

Reported

function isAfter(left: int32, right: int32): boolean {
    return left >= right + 1;
}
Accepted

function isAfter(left: int32, right: int32): boolean {
    return left > right;
}
Prior art

- Clippy · intplusone

language/linter/src/rules/style/manualstrictcomparison.rs:8