Linters *are* a good idea. Reducing cost of finding errors of certain classes is a valuable thing. In https://github.com/rust-lang/rust-clippy … we are quite conservative with what we lint by default, and by design there are many allow-by-default lints. Style is only linted when leading to errors.https://twitter.com/stephentyrone/status/1113517895475240961 …
-
-
So that means there is no value in linters that point out errors we cannot automatically fix? I disagree, of course, but would like to know why you would think this?
-
I guess it depends what you call a linter. I'm talking about cosmetic linting vs static analysis tooling. E.g. I wouldn't call borrowck a linter. If it's a stylistic suggestion it should be implemented automatically IMO. Otherwise making it a hard error wastes coworkers time.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.