Talk:Monads/Maybe monad: Difference between revisions
Content added Content deleted
| Line 13: | Line 13: | ||
* there might be scope for framing these tasks more in terms of a class of '''problem''' than a class of solution ? [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 20:37, 4 February 2016 (UTC) |
* there might be scope for framing these tasks more in terms of a class of '''problem''' than a class of solution ? [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 20:37, 4 February 2016 (UTC) |
||
: I agree - or, more specifically, I could accept either interpretation. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 21:14, 4 February 2016 (UTC) |
: I agree - or, more specifically, I could accept either interpretation. --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 21:14, 4 February 2016 (UTC) |
||
:: I suppose I see the deeper problem as the tension between structure (often nested) and sequence (often threading more than one strand of data). Not sure if that resonates with the J case. Does J have a more natural way of avoiding/handling exceptions when a input somewhere inside a function nest is out of range ? (or is 'function nest' perhaps a less relevant form of tructure in the array model ?) [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 21:37, 4 February 2016 (UTC) |
|||