Talk:Loops/Wrong ranges: Difference between revisions

From Rosetta Code
Content added Content deleted
m (→‎The idea: Tep.)
Line 9: Line 9:


:: Yea, I came back to find six examples and noone complaining so thought ... [[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 06:44, 17 September 2018 (UTC)
:: Yea, I came back to find six examples and noone complaining so thought ... [[User:Paddy3118|Paddy3118]] ([[User talk: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. I can't see anything in the task description that says that a loop must be used, but is this intentional? In other words, are the Julia and R solutions acceptable? --[[User:ReeceGoding|ReeceGoding]] ([[User talk:ReeceGoding|talk]]) 17:28, 22 June 2020 (UTC)

Revision as of 17:28, 22 June 2020

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. I can't see anything in the task description that says that a loop must be used, but is this intentional? In other words, are the Julia and R solutions acceptable? --ReeceGoding (talk) 17:28, 22 June 2020 (UTC)