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 …
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.
-
-
I won't call borrowck a linter either. I still call all the linters in clippy what they are. They find & report certain constellations in the code that cost perf or may mislead. They can be deactivated either by annotation, a config or the command line. Some have automatic fixes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.