Talk:Loops/Wrong ranges

From Rosetta Code

The idea

Thanks to Gerard for this inspiration.

The examples show that range functionality varies between languages. If moving between languages you need to make the effort to understand the new functionality. It was pointed out that the values are not "Wrong" and may have well defined actions in a language: I apologise, but just loved the mild tongue twister in "wrong ranges" :-)
Paddy3118 (talk) 19:46, 16 September 2018 (UTC)

This draft task sure made it to task status pretty fast, by gum.   -- Gerard Schildberger (talk) 03:31, 17 September 2018 (UTC)
Yea, I came back to find six examples and noone complaining so thought ... Paddy3118 (talk) 06:44, 17 September 2018 (UTC)

Does this task require a loop?

Following the Julia solution, I've just submitted an R solution that does not contain a loop. The task title makes me think that this is foul play, but I can't see anything in the task description that says that a loop must be used. Is this intentional? In other words, are the Julia and R solutions acceptable? --ReeceGoding (talk) 17:28, 22 June 2020 (UTC)

No. Other than the title, there is no mention of loops anywhere in the task description. Sequences and loops are somewhat orthogonal anyway. If your language has some special syntax that is commonly used to generate sequences, then that is probably more interesting/useful than a slavish "do it with an explicit loop" example IMO. --Thundergnat (talk) 21:16, 22 June 2020 (UTC)
Yep Thundergnat is correct. Although inspired by a loop, it is written to include sequence generators. The Python solution is such, and it may be better if languages use such given a choice. I guess I left it up to the example writer but didn't comment on this. Good to have it in the talk page now 👍. --Paddy3118 (talk) 02:50, 24 June 2020 (UTC)