Re:Why I love Rust for tokenising and parsing
by aftbit on Friday November 08, 2024 @10:38AM
(#42087636)
You're intended to run gofmt on every save. golang is designed to be a sort of straight-jacket that forces everyone to write code in the same way (style etc) so that the junior devs can understand it clearly.
[ Parent
| on HN ]
Re:Why I love Rust for tokenising and parsing
by grey-area on Friday November 08, 2024 @10:55AM
(#42087783)
And so that people (of any level) don't bikeshed over silly things like tabs and spaces or { and newlines.
I really like this about go - that it formats code for you, and miss it in other languages where we have linters but not formatters, which is a terrible idea IMO.
Re:Why I love Rust for tokenising and parsing
by umanwizard on Friday November 08, 2024 @01:55PM
(#42089483)
What mainstream languages don’t have formatters nowadays? Rust has rustfmt, C and related languages have clang-tidy, python has Black…
Re:Why I love Rust for tokenising and parsing
by grey-area on Friday November 08, 2024 @03:57PM
(#42090419)
I mean built in that everyone uses. There are of course third party formatters.
Re:Why I love Rust for tokenising and parsing
by umanwizard on Friday November 08, 2024 @05:09PM
(#42090867)
You can force everyone on a project to use a formatter just as easily in any of those languages as you can in Go, with a few lines in your CI job definitions. Whether they're third-party or not is irrelevant.
Re:Why I love Rust for tokenising and parsing
by Mawr on Saturday November 09, 2024 @05:46AM
(#42093695)
It's not irrelevant, it's the entire point. The whole Go ecosystem uses a single formatter. There's no need to force anyone, everyone just uses gofmt. You will not be able to replicate that level of ubiquity easily at all.
Re:Why I love Rust for tokenising and parsing
by umanwizard on Saturday November 09, 2024 @09:13AM
(#42094523)
Not really true because you have both gofmt and gofumpt, and gofmt can be run with -s or not, and also lots of projects are using separate linters to enforce maximum line length.
Re:Why I love Rust for tokenising and parsing
by mikeschinkel on Saturday November 09, 2024 @10:01PM
(#42098344)
But true enough.
Re:Why I love Rust for tokenising and parsing
by guappa on Monday November 11, 2024 @02:28AM
(#42105146)
Not true. Because after running go fmt and pushing our CI fails because of other stylistic concerns that are checked by another tool.
Re:Why I love Rust for tokenising and parsing
by mikeschinkel on Saturday November 09, 2024 @10:00PM
(#42098338)
You can only force everyone on a project to use a formatter if you are the one who has the authority to decree what will be done on the team. OTOH, if you are but a team member and you join a team where the manager does not think common formatting is important, then you get f*ck all.
So being built-in, idiomatic and expected cannot be over-appreciated.
Re:Why I love Rust for tokenising and parsing
by mistrial9 on Friday November 08, 2024 @02:41PM
(#42089853)
that's your preference but not universal
Re:Why I love Rust for tokenising and parsing
by grey-area on Monday November 11, 2024 @06:22AM
(#42106323)
My only preference is not to have to think about whitespace etc. I guess others who feel differently certainly wouldn't like Go, and that's ok!
Re:Why I love Rust for tokenising and parsing
by guappa on Monday November 11, 2024 @02:32AM
(#42105176)
Why are you talking about go fmt? I'm talking about parser of the go language
If I write
if x
{
bla
}
it will not compile, because the { needs to be on the same line as the X (for no reason whatsoever).