zlacker

[parent] [thread] 5 comments
1. raveni+(OP)[view] [source] 2025-12-03 18:25:15

  continue was called loop for some reason
How strange! Does anyone know why?
replies(2): >>kureso+P1 >>stevek+O5
2. kureso+P1[view] [source] 2025-12-03 18:34:03
>>raveni+(OP)
I could see it… like “loop back around” or “continue loop”. I think good old “continue” is better and more familiar though :)
3. stevek+O5[view] [source] 2025-12-03 18:52:33
>>raveni+(OP)
There was an early rule that Rust keywords should be five characters or less. I would guess it's because of this rule. I believe loop turned into cont to satisfy this rule, and then eventually we relaxed the rule, and it became continue.
replies(1): >>iknows+if
◧◩
4. iknows+if[view] [source] [discussion] 2025-12-03 19:39:40
>>stevek+O5
Whoa, do you know who and why came up with that? So strange, making it less readable on purpose?
replies(2): >>stevek+do >>Deflet+1p4
◧◩◪
5. stevek+do[view] [source] [discussion] 2025-12-03 20:19:06
>>iknows+if
IIRC it was just a personal preference of Graydon's back then. I'm also not sure it was intended to live forever, just something to try and nudge things in a particular direction.

Terseness doesn't inherently mean less readable.

I do think that that rule is probably not one that would be good permanently.

◧◩◪
6. Deflet+1p4[view] [source] [discussion] 2025-12-04 23:50:43
>>iknows+if
Probably for the same reason that most new language these days cannot bring themselves to just use "function" and instead have "fn", "fun", "func", etc. It's a headlong pursuit of conciseness for the sake of conciseness.
[go to top]