Twitter | Pretraživanje | |
Saoirse Shipwreckt 31. sij
I still don’t understand why everyone blocks their CI on unimportant formatting lints
Reply Retweet Označi sa "sviđa mi se"
Saoirse Shipwreckt
When I want to make a small addition to a big project setting up the tool chain to run your linter locally is an enormous barrier to entry
Reply Retweet Označi sa "sviđa mi se" More
Saoirse Shipwreckt 31. sij
Odgovor korisniku/ci @withoutboats
All of this so that I don’t include new lines some rule has decided are unnecessary??
Reply Retweet Označi sa "sviđa mi se"
Saoirse Shipwreckt 31. sij
Odgovor korisniku/ci @withoutboats
Not criticizing the rust compiler team here, this is standard practice across open source projects and I just don’t understand the obsession with “consistent formatting” - who cares??
Reply Retweet Označi sa "sviđa mi se"
Cecile Tonglet 🦀 1. velj
Odgovor korisniku/ci @withoutboats
I definitely agree on that. I didn't know it was that complicated to get into the rust project itself. I heard rustfmt took some time before reaching a certain maturity level. Maybe it's related, after all rust is the most ancient rust project I guess
Reply Retweet Označi sa "sviđa mi se"
Saoirse Shipwreckt 1. velj
Odgovor korisniku/ci @CecileTonglet
It’s perfectly natural that any projects tooling assumes you have set up a build environment. It just so happens that setting up a build environment for rust takes upwards of hours
Reply Retweet Označi sa "sviđa mi se"
Mazdak Farrokhzad 1. velj
Odgovor korisniku/ci @withoutboats
By the way, if you haven't already, I recommend setting up VSCode with rust-analyzer and then using format-on-save. This lets me write code in a terrible but quick way, ignoring style entirely, and I never have issues with the rustfmt check in CI.
Reply Retweet Označi sa "sviđa mi se"