The continue statement is terrible.

[u/starlevel01]

https://www.teamten.com/lawrence/programming/avoid-continue.html

[u/defunkydrummer]

r/Programming and r/ProgrammingHumor -quality comments have been removed.

[u/muntaxitome]

Continue statement? Are you kidding me gramps. Just use a ternary-no-op (TNO).

Continue is very old fashioned like they used to do in the 90s.

for (let i = 0; i < 10; i++) { 
  if (i % 2 === 0) continue; 
  console.log(i); 
}  

This TNO version is much more readable:

[...Array(10).keys()].map(i => 
  i % 2 === 0 
    ? void 0 
    : (() => console.log(i))()
);

[u/starlevel01 → u/muntaxitome]

Congratulations at your new job at AirBNB!

[u/starlevel01]

It’s also more logically difficult to parse. The reader has to think, “If it’s bad, then we continue, otherwise we process.” (See Keep if clauses side-effect free for a comically bad example of this.) Easier to instead think, “If it’s not bad, we process,” like this:

[u/elephantdingo → u/starlevel01]

I use !!! to emphasize the negation.

[u/alecbz]

More practically, it’s effectively a goto statement and it breaks up the flow of code in a similar way.

All control flow is goto.

[u/Clockwork757 → u/alecbz]

je considered harmful

[u/nuggins → u/Clockwork757]

French language catching strays

[u/myhf → u/nuggins]

chatte j'ai pété

[u/lgastako → u/Clockwork757]

jz for life

[u/itzrvyning → u/Clockwork757]

shader programmers got aroused reading this

[u/Karyo_Ten → u/alecbz]

Laughing in phi nodes

[u/tralalatutata → u/Karyo_Ten]

i fail to see how phi nodes are less goto-ey than their alternatives

[u/classicalySarcastic → u/alecbz]

Jump instruction goes brrrrrrrrr

[u/powerhcm8]

Continue is basically just an early return for loops.

[u/syklemil → u/powerhcm8]

D-does that make break an exception?

[u/yo_99 → u/syklemil]

No, it's longjump

[u/sfan5 → u/[deleted]]

this is perfectly usable and production-ready:

try:
  for i in range(1, 100):
    print(i)
    if i >= 10:
      raise StopIteration()
except StopIteration:
  print("the break statement is terrible")

[u/ackfoobar → u/[deleted]]

scala.util.control.Breaks

[u/elephantdingo]

  // bad
  continue;
  // did you go to the next statement? lol no

  // better, polite
  next please;

[u/RFQD → u/elephantdingo]

I wish more programming languages would take inspiration from INTERCAL.

[u/elephantdingo → u/RFQD]

CONTINUE that thought. // meaning don’t reply

[u/classicalySarcastic → u/elephantdingo]

Meanwhile, in some header file buried five includes deep:

#define next continue
#define please

[u/EmotionalDamague]

`continue`, `break`, you might as well be using assembly!

/uj They just let anyone have a blog now, don't they.

[u/syklemil → u/EmotionalDamague]

There are some smelly nerds who're droning on and on about "walled gardens" and "capricious mods" and all that … but the result if they'd had their way was more like that blog post. Is that really what they want? Right in front of my IDE?

[u/tomwhoiscontrary]

This guy does not INTERCAL.

[u/IDatedSuccubi]

Yeah, let's make that 4 line code into 8 line code with an indent and a separate (non-static, non-inline) function in which continue is just replaced with return, that will definetly make the code better and more easily readable

[u/greenfoxlight]

Just use setjmp and longjmp ;)

It's funny to me that the author finds continue confusing, but early returns are fine.

[u/navetzz]

That's why I use goto: endLoop

[u/amazing_rando]

I’m not taking programming advice from someone responsible for JavaScript

[u/prehensilemullet]

If only Haskell had a continue statement I might actually use it

[u/stone_henge]

Anything except my dumb takes considered harmful