|
@withoutboats | |||||
|
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
|
||||||
|
||||||
|
Saoirse Shipwreckt
@withoutboats
|
31. sij |
|
I still don’t understand why everyone blocks their CI on unimportant formatting lints
|
||
|
|
||
|
Saoirse Shipwreckt
@withoutboats
|
31. sij |
|
All of this so that I don’t include new lines some rule has decided are unnecessary??
|
||
|
|
||
|
Saoirse Shipwreckt
@withoutboats
|
31. sij |
|
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??
|
||
|
|
||
|
Cecile Tonglet 🦀
@CecileTonglet
|
1. velj |
|
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
|
||
|
|
||
|
Saoirse Shipwreckt
@withoutboats
|
1. velj |
|
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
|
||
|
|
||
|
Mazdak Farrokhzad
@etareduced
|
1. velj |
|
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.
|
||
|
|
||