Talk:Range consolidation: Difference between revisions
Content added Content deleted
(→Python tester: handle case where algorithm could generate new, wrong, ranges.) |
m (→null range: added a new talk section.) |
||
| Line 21: | Line 21: | ||
Hi Thundergnat, I state "covering all numbers between and including both bounds"; (other boundary types not used in the task). It could be similar to the task you mention. A quick look leaves me wondering if this consolidation could use the operators mentioned? --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 15:17, 3 February 2019 (UTC) |
Hi Thundergnat, I state "covering all numbers between and including both bounds"; (other boundary types not used in the task). It could be similar to the task you mention. A quick look leaves me wondering if this consolidation could use the operators mentioned? --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 15:17, 3 February 2019 (UTC) |
||
==null range== |
|||
Is a ''null'' range a legal and valid range? Should programming examples handle (and express) such an animal? -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:38, 9 February 2019 (UTC) |
|||
==Python tester== |
==Python tester== |
||