Go is a very opinionated language which is why I was so lucky for their opinion on this (and other things) to agree with mine.
And who can forget this abomination
while (x == y) { func1(); func2(); }
Aka the bash one-liner
The eternal holy wars rage on
If prefer two spaces per indention instead of tabs, but otherwise I agree with the choice of style.
Tabs has no place in code, just recently I started a project with four space indentation, that quickly got changed to two.
Allmans what I learnt then went to K&R on my own because it made more sense to me. I think GNU is fine I guess, not the others though. Not that what I say matters I've forgotten how to code and can barely do Hello World these days.
Why would a development environment show you code in a different style from what you like? It's a simple conversion.
Why would your IDE show you code in a language other than you prefer? It's just a conversion.
Even my web browser shows any text in languages I can read, but for some reason it doesn't let me edit a document through the translation.
On a serious note tho, I never understood the benefits of GNU's spaces after functions. I don't really mind most of the rest but I just don't get the benefits of 'funcname (arg)' vs. 'funcname(arg)'. Is there a specific reason for this? Personally, I find this to reduce readability because I have to think for a split second whether I'm looking at a variable or a function call.
Of cause this is also due to my habits, but I'm curious as to what the reasoning is.
Honestly I think it's just "spaces before open parens" and at least it's consistent. K&R, which I use, wants spaces before the parens in conditionals and loops but not in method sigs or method calls and the linter at work gets me almost every time I type the word "if".
Fair enough if the GNU dudes valued consistent spacing more than taking function calls as one "logical block". Not my cup of tea but that's what configurable auto formatting is for.
Allman is a benign neurosis
That's why Python has a superior syntax. There is usually one obvious way to do it, and that's the right way.
fixed?? 😳😳
This is the way
I want a language that takes this and has a specification for the editor to prettify it
while x==y
func1
func2
Crockford gang approves.
I might argue that rhe syntax of God's language is the one true syntax.
I am tired and unmotivated so I probably won't though.
Be sure to follow the rule before you head out.
Rule: You must post before you leave.