Rust lints passes are often part of the compiler. The difference is that there's a way to disable lints.
-
-
Replying to @wycats @michaellnorth and
so closer to -Werror -Wall than to eslint?
1 reply 0 retweets 0 likes -
Replying to @bassjacob @michaellnorth and
Right. We also use lints a lot to help people migrate away from bad practices or as part of transitional plans.
1 reply 0 retweets 0 likes -
Replying to @wycats @bassjacob and
Lints make it possible to be in "prototype" mode to quickly sketch something out and then go into "hard error mode".
1 reply 0 retweets 0 likes -
Replying to @wycats @bassjacob and
Things like dead code and unused imports/params lints are very annoying when prototyping or refactoring but good when done.
1 reply 0 retweets 0 likes -
Replying to @wycats @bassjacob and
Another example: use of private types in a public signature. Requires sophisticated compiler support but annoying while prototyping.
1 reply 0 retweets 0 likes -
Replying to @wycats @bassjacob and
I should be clear that refactoring is probably a more dominant use of this "mode" than prototyping.
1 reply 0 retweets 1 like -
Replying to @wycats @michaellnorth and
Sounds like a really nice DX-level tweak. clearly a lot of thought goes into the day to day!
1 reply 0 retweets 1 like -
Replying to @bassjacob @michaellnorth and
Can confirm! 2017 has been all abouthttps://blog.rust-lang.org/2017/03/02/lang-ergonomics.html …
1 reply 0 retweets 1 like -
Replying to @wycats @michaellnorth and
implicit vs explicit resonates strongly. I love the focus on the end-user and their experience. sounds very welcoming
1 reply 0 retweets 0 likes
We try not to be too religious but extract useful learnings from the various camps by giving things thought
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.