Talk:Cumulative standard deviation: Difference between revisions
m
→Function takes vector/array or single value?
(→Function takes vector/array or single value?: Many examples deviate.) |
|||
Line 12:
Many examples (too many), have not paid attention to the task description. I've started to mark those but it is a long job... Please remember that if your language cannot match some aspect of the task description then state this clearly, up front and describe what aspects of the task you can follow. (Note, that is if your language cannot do something - not merely if your example does not follow the task). The J language example goes about it in this way, I guess if you had a "pure" functional language that did not allow functions to save state between calls then you might need to explain this at the beginning of your example as well as what compromises this lead to. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 22:16, 16 June 2015 (UTC)
: Rather than "cannotdo something" I would prefer the more accurate "should not do something". Presumably the focus on the detail of how the incremental process works has something to do with ideas about efficiency? But, depending on the language, this level of micromanagement might make things considerably more inefficient than they would be otherwise - I have seen this kind of issue lead to timing ratios where one implementation would be over 9000 times faster than the other for some test data sets (though smaller differences are also possible and I try not to care when the difference is less than a factor of 2 -- modern machines introduce variations which can easily reverse a "less than factor of 2" performance issue). --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 10:33, 17 June 2015 (UTC)
| |||