Re:Implications of Rewriting a Browser Component in Rust
by Twirrim on Thursday February 28, 2019 @10:38PM
(#19277730)
Use a linter. Most IDEs will do it for you natively, and even if you're dealing with a terminal based editor like vim, it's really easy to get the output of pylint, flake8 etc. running in it. It's extremely rare I ever get a syntax error make it through to code review, let alone build/deploy.
[ Parent
| on HN ]
Re:Implications of Rewriting a Browser Component in Rust
by baroffoos on Thursday February 28, 2019 @10:48PM
(#19277770)
Linters catch the easy cases but when the problem spans multiple files they have no clue what is going on.
Re:Implications of Rewriting a Browser Component in Rust
by ShinTakuya on Tuesday March 05, 2019 @12:32AM
(#19308330)
The mypy type linter performs type checking across files, in many cases even without explicit annotations.