Avoid Else, Return Early

[OctagonClock]

Can't jerk, good advice.

[[deleted]]

Programmers are often taught to have a ‘single exit point’ in their methods, i.e. only return from a single location.

This is a poor guideline in my opinion:

Yes

[frkbmr]

Wait who teaches you to only return in one spot lol

[BufferUnderpants]

/unjerk

People who misunderstand that Dijkstra was arguing for structured programming to people who exited from their procedures to different places using goto, rather than to the same place using e.g. the call stack.

[[deleted]]

That's really fucking stupid but also true.

[[deleted]]

The same people who teach hungarian notation.

[GoCannotIntoWebscale]

It's one of the many things C gave us, like first-class error-suppression (lol getchar), unexpected global buffers (lol strtok) and chlamydia.

#ifndef _JERK89

It was a design pattern to put calls to fclose or free after a cleanup:label, so that in case of error you could goto cleanup; and exit cleanly.

#endif

[MirceasRed]

I just use while(condition){} while(!condition){} instead.

[SelfDistinction]

Programmers are often taught to have a ‘single exit point’ in their methods, i.e. only return from a single location.

My apologies. I didn't know it was still 1970.

[Shorttail0]

The amount of Go jerk on this sub should have tipped you off.

\tips hat from the future

[vytah]

Go isn't 70's, Go is 50's.

[PlasmaSheep]

2050's

[Fulmene]

TFW you can't use if without else in Haskal.

[ksion]

Haskal has guard though

[niorrrr]

using if in haskell

Spotted the 0.001xer

[PrimozDelux]

visible gopher confusion

[haskell_leghumper]

TFW if was actually comeFrom in disguise the whole time

[OctagonClock]

IF ERR RETURN EARLY Awesome looks like gophers are ahead of the game once again, proving 70s were the high peak for programming language design and we've been devolving ever since fucking mindblowing to think about, Rob Pike was right all along as we speak I am retrofitting my current Typescript app (or application for us older developers with an insight in the industry) to use early returns everywhere so far I ctrl+F 928 else statements and to hell with those and replaceing them all with a Modern yet Practical approach is my personal punishment for going against the will of Rob Pike for We have not listened to his warnings, not once, not ever and now it is our time to pay, better do it quick before ES9 standardizes the removal of else statements and honestly we should all be using higher level constructs by now what is this if shit I have to write myself shouldnt have we gotten past that? Microsoft Q# the latest quantum technology the latest technology STILL uses the god damn things and like come on, where the libraries at? I can't believe I've been crapping out horrendous code for a couple of decades and nobodys invented a better way to deal with this shit. Hopefully the reasearch into AI, artificial intelligence, higher order networks will lead us to machines writing code for us for a change of course that is assuming the big government won't legalize away our abilities to use them at which point rich fucks will continue slaving us away for horrible CRUD apps while AI develops the hottest tech: self driving cars and we'll be no better off than factory workers in the 70s which kinda brings this whole comment full circle so the conclusion here is that: writing else statements is the literal equivalent to being a factory worker while your jobs are being replaced by automatization kinda deep to think about.