|
@withoutboats | |||||
|
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
|
||||||
|
||||||
|
Saoirse Shipwreckt
@withoutboats
|
31. sij |
|
Automatic formatting rules consistently make actual code worse! Casing rules and common indentation are literally all you need
|
||
|
|
||
|
10x Milkshake™
@flukejones
|
1. velj |
|
For each consecutive argument in a function I indent 2.5 spaces. Ending braces are indented an amount of spaces equal to the line distance from the start brace - brilliant for visualising the amount of lines in a block.
|
||
|
|
||
|
Cecile Tonglet 🦀
@CecileTonglet
|
1. velj |
|
Use a non-breaking space (0xa0) after the words impl, struct, enum and mut
|
||
|
|
||
|
Jeremy Fitzhardinge
@jsgf
|
1. velj |
|
Yeah rigorous formatting rules ignore the fact that formatting can (and should) have semantic value.
|
||
|
|
||
|
InsanityBit
@InsanityBit
|
31. sij |
|
Enforced code formatting is GARBAGE.
I have keratoconus and what works for other people absolutely, 100% does not work for me. I zoom in 200% on every screen, I add spacing between lines, etc.
If you enforce stupid layout shit I'm not touching the language.
|
||
|
|
||
|
to kubectl or not to kubectl that is the question
@mgattozzi
|
31. sij |
|
people should be able to customize how it looks to you and stored in whatever format. Some people need really wide tabs and large text as an accessibility thing, but all the software doesn't really do that, so then it chooses spaces.
twitter.com/mgattozzi/stat…
|
||
|
|
||
|
ven
@vengarioth
|
31. sij |
|
i think this is the sanest take on that topic.. always love auto formatters moving my 4x4 matrix declarations around..
|
||
|
|
||
|
Florian Gilcher ∠(・.-)―〉 →◎
@Argorak
|
16 h |
|
Hello!
github.com/http-rs/http-c…
|
||
|
|
||