Talk:Type detection: Difference between revisions
→Perhaps "Type detection" could usefully be reworked as '''search a tree''' or '''search a nested list'''
No edit summary |
|||
Line 47:
( It may also be worth looking at some existing tasks which already demonstrate type-conditional evaluation or flow – ''flattening lists'', for example – just to check that something more focused is really required. There are probably also many tasks which demonstrate evaluation or flow which is conditional on the particular type of numeric values – maybe what is really needed is an index, rather than an additional task ) [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 18:34, 9 October 2015 (UTC)
==Perhaps search a nested list or tree ?==
A natural context for type-conditional evaluation or flow is a search for a value through the leaves of a tree, or through the sub-lists of a nested list/array.
I may be missing something, but I haven't spotted a task that immediately looks like '''search a tree''' or '''search a nested list'''. If there is such a gap, I think that perhaps 'Type detection' could usefully be reworked and reframed (possibly retitled ?) to fill it.
[[User:Hout|Hout]] ([[User talk:Hout|talk]]) 14:52, 10 October 2015 (UTC)
| |||