Rename 'cont' to 'next'

[brson]

'cont' sounds offensive, especially when spoken aloud. There's precedent for 'next' in other languages.

Remember to change the docs.

[catamorphism]

Bikeshed: how about "skip"? It seems like variables are more likely to be named "next" than "skip".

[jamorton]

Is there anything wrong with continue?

[brson]

@Jonanin continue is 8 characters! In Rust we have a 5 character keyword limit.

But seriously, that's the reason.

[jamorton]

... alright ...

interesting, I guess :]

[boggle]

A good rule is justified by it's exceptions. 'Next' is a very common variable name in linked lists and other data structures, I find 'skip' to be frequently used for boolean flags, while 'continue' is rarely used. That may be quite subjective but I'd rather have rust adopt 'continue'. As a compromise, I'd vote for 'resume' (which is a keyword in BASIC).

[pcwalton]

I like skip.

[bstrie]

Repasting from my mis-comment in 2233:

Also keep in mind how the keyword will sound with the labeled break/continue from #2216. For a loop labeled foo, saying skip foo sounds (sort of) like you're telling it to skip the next iteration of foo.

I submit pass, which has precedence as a keyword from Python (though with a different meaning here).

[graydon]

We talked about this on IRC yesterday and stumbled into the pleasing possibility of making loop; on its own (no following brace) be the expression for continuing-to-loop. I kinda like that. One fewer keyword!

[jsternberg]

I think overloading loop to have two different meanings is confusing. I also don't like the idea of using pass as a keyword for this specific use, because, as Wensleydale said, pass means something completely different in Python (if that's the intended reason to use that keyword). I also don't think it really addresses the original problem (pass foo is just as weird as skip foo).

I do like the skip keyword. I think it pretty clearly says what the keyword is doing.

[boggle]

Opinions on resume (I know one char too long)? Don't mind using skip either but resume has the precedence of having been used for continue in BASIC.

[brson]

I like resume better than skip, pass, and loop. I'm also thinking that continue isn't bad and maybe this 5-character rule is hurting us by forcing us to pick worse and worse keywords.

[mitsuhiko]

I honestly think the short keywords are hurting rust. log already conflicts with very common function names, same with next. prev/next are very common function names or properties (linked lists come to mind).

[bstrie]

@mitsuhiko #554 could turn log into a syntax extension, in which case it would invoked as #log and would no longer collide with user-defined functions.

[brson]

OK this is a trivial change to make but we don't have a clear consensus - I'm not even sure there's consensus that we want to change cont. There seem to be a lot of preferences for skip. My current preference is for continue.

[graydon]

My preference lies with loop since it's already reserved and we're in a keyword-cutting mood. next is my next choice, but the collision with other identifiers is legitimate (unless our keywords are to become contextual, somehow; but I think this context is pretty unavoidable).

How about again?

[nikomatsakis]

I like loop too.

[kingcons]

I like loop. Hell, you could do "recur" if you really felt like it...

[kud1ing]

On Reddit someone suggested Perl’s "redo".

[jsternberg]

I don't like redo. redo implies your repeating something instead of iterating (which is what continue does).

[graydon]

We're going to go with 'again'. Did some surveying and it's the least-objectionable one that fits in the length rule.

[anacrolix]

next from Perl? Perl also has last (like break).