Talk:Mian-Chowla sequence: Difference between revisions

Line 1:

== Distinct? ==

Hi, could you further explain what distinct means in the task description? Thanks. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:50, 15 March 2019 (UTC)

: Scrub that, The OEIS entry made sense to me. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 09:54, 15 March 2019 (UTC)

:Means a unique sum. E.G. 3 can't be in the sequence since 1 + 3 = 4 and 2 + 2 = 4. --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 12:07, 15 March 2019 (UTC)

== Execution Speed? ==

Hi, it could be nice to have as a third task, the program duration. This gives an indicator of the language efficiency (and the algorithm too). I have tried among several Basic language implementations and the elapsed time, for 100 terms, is spread between 2 seconds and 25 minutes ! --[[User:PatGarrett|PatGarrett]] ([[User talk:PatGarrett|talk]]) 11:48, 15 March 2019 (UTC)

:In general, Rosettacode discourages emphasizing program execution speed. It is more about comparison of concepts, and focusing on speed tends to lead to heavily optimized code which may become difficult for a new language user to read. It is sometimes useful, or at least entertaining to have an idea of relative execution speeds, but I hesitate to make it, or even imply that it should be, a requirement.

:When I am developing tasks, I try to choose goals that most languages should be able to do in about a minute or less of processing time. Selfishly in some part, because all Perl 6 RC entries are run daily against a nightly development build of blead Perl 6 for smoke testing, so tasks that take excessively long really extend the testing time. (Running ~1000 or so tasks takes a while even if they ''aren't'' excessively long.) --[[User:Thundergnat|Thundergnat]] ([[User talk:Thundergnat|talk]]) 12:07, 15 March 2019 (UTC)