Can we all agree haskell style is a mental disorder?
I think it’s trying to keep track of all the semicolons but my god does it look strange
I might just do that style just to make my professor cringe on my next c# assignment
“I mean, it’s right, it runs, but it looks like shit”
You might get a kick out of this
https://en.m.wikipedia.org/wiki/International_Obfuscated_C_Code_Contest
It’s a competition? Damn, that’s wild XD
One of the benefits of the haskell style is easy commenting of the additional functions. I do something similar in my python scripts when testing several differnent chunks of code.
But then again I chose a career in GIS so I probably have a mental disorder.
deleted by creator
I went from not being able to tell the difference to being deeply disturbed by everything in the red
K&R 4evah
What is Lisp style, Lisp doesn’t have this syntax? Or is it referring to something other than Lisp languages. Same with Haskell.
Haven’t coded with Lisp, but I’ve seen Lisp codes that are formatted like that. Haskell too.
Perl style: all on one line, with the ‘while’ statement at the end.
Ew. I usually don’t use curly braced languages. But whenever I need to define collections on multiple lines I always put opening bracket on the end of the line and closing bracket on the same indent level as the start of the statement:
let hello = [ "Hello, there!", ] var a = true arr = [ "line 1", "line 2", ]Just run with the default style of the de-facto formatter for whatever language you are using. It’s really not worth any mental effort.
This is true, but it also moves the discussion to which is the superior code for matter for languages that don’t have a clear default option, and of course to which languages have the best formatters.
I have a hard stance in this question - code formatters should be deterministic on any given syntax tree - there should be no leeway for choosing how any given piece of code formats. Seriously. If your anti-bikeshedding tool does not completely eliminate the bikeshedding, you have not done your job correctly.
But it’s fun to argue over
GNU > Allman
I’m Ratliff and K&R style.
Can we talk about variable scope? Is x changing inside a called function without so much as a pointer being passed?
Avoiding global variables is just something dumb people do to protect themselves. Real programmers declare every variable before Main.
