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
-
Prikaži ovu nit
-
Automatic formatting rules consistently make actual code worse! Casing rules and common indentation are literally all you need
0 proslijeđenih tweetova 13 korisnika označava da im se sviđaPrikaži ovu nit
Odgovor korisniku/ci @withoutboats
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.
06:38 - 31. sij 2020.
0 replies
0 proslijeđenih tweetova
3 korisnika označavaju da im se sviđa
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.