Anonymous user
Talk:Range consolidation: Difference between revisions
→The nature of these ranges, and thus of the task, is not yet clear: On normalization...
(→null range: zero-extent ranges) |
(→The nature of these ranges, and thus of the task, is not yet clear: On normalization...) |
||
Line 14:
:To be able to asily compare outputs it seemed that a sorting should be devised so that all outputs would be similar, but, I wanted to impose no such limitation on inputs, so programs may have to pre-condition/normalize inputs depending on their code.
::There is no need to pre-condition/normalize inputs. Consider a range type on which I define addition and subtraction. The task then becomes adding the supplied list of lists of test ranges to an empty range. So the first case would be let n=[()]+[(1,1)] then let g=n+[(2,2)]. Of course I wouldn't dare improve this task by adding extra credit, but I shall give extra credit to those solutions implementing subtraction.--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 14:13, 10 February 2019 (UTC)
:::''"There is no need to pre-condition/normalize inputs."''
:::Thats right, just '''output''' normalisation is mandated. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 18:52, 10 February 2019 (UTC)
:Pythons pre-normalization is an integral part of its algorithm. (Which I have not yet fully tested}.
| |||