Talk:Type detection: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
Line 1:
Hi, Is this the start of a draft task? --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 12:57, 7 October 2015 (UTC)
:# '''Questions:''' Is ''type detection'' itself a task ? What problem might I be trying to solve by detecting a type (at run-time) in the compiled version of a statically typed language ? Are you, for some reason, thinking of a class of problems which can't be solved in terms of an untyped lambda calculus ? If so, what are they ? Does this sound like a Rosetta task (the value of which is that languages turn out to be '''unexpectedly similar beneath the surface''', if you set them all to the same task) ? Or is it a stamp-collector, list-maker or grammatical librarian's task (simply absorbed in the cataloguing of notational '''differences''') ?
:# '''Thoughts:''' The message of Rosetta is that you get deep insights when different languages are coming at the same non-linguistic task from their own distinctive angles, rather
:A task to which Miranda, Haskell or OCaml users might respond by saying '''not really relevant''', '''doesn't really arise outside the REPL''' or '''doesn't arise at all''', would probably be too superficial, and a bit of a waste of potential for insight and comparison.
:In short – what is the concrete problem (outside the language) for which the solutions may include branching on types ? What is the actual task ? How would you frame it so that it scored well as a Rosetta task in terms of the 3 values formulated on the landing page:
|