|
@withoutboats | |||||
|
Automatic formatting rules consistently make actual code worse! Casing rules and common indentation are literally all you need
|
||||||
|
||||||
|
Saoirse Shipwreckt
@withoutboats
|
31. sij |
|
My real hot take: you do need some formatting consensus, but nothing more than Rust has had since before 1.0:
- what a normal indentation is
- what casing is used for each kind of name
Nothing else! Beyond that every decision should be made contextually by the code author
|
||
|
|
||
|
kornel@mastodon.social
@kornelski
|
31. sij |
|
Yes! I love that gofmt doesn't have an opinion on whether a construct should be 1-liner or in multiple lines. It lets me to keep boilerplate compact, and draw attention to the tricky parts of the code.
|
||
|
|
||
|
Steve Donovan
@StevedInJoburg
|
31. sij |
|
My beef is that rustfmt does not like space after '!' which has been my style for years. Might start using postfix '.not()' to make negation obvious again! Anyway, lost this battle at $work so moving on
|
||
|
|
||