4 ms·
> Also, plenty of linter errors are actual errors that need non-trivial fixing. These sound like they're not lints at all.
by insanitybit 3y ago
> Also, plenty of linter errors are actual errors that need non-trivial fixing.
These sound like they're not lints at all.
- crabbone 3y agoNo, not really. It is perfectly possible to write unintentionally valid code, which would be caught by linter due to the author not following some convention. Trivial and popular example of such code is assignment instead of comparison in the context of condition. Some languages allow for this to happen, but it's known as a possible mistake and so the conventions in such languages would discourage the use of assignment in the context of condition, even though it technically produces valid code.