Re:Why we're supporting Typed Clojure
by ambrosebs on Friday September 27, 2013 @08:08PM
(#6460319)
Yep that's correct. I want a tool that infers a rough approximation of top-levels to accelerate the process of porting untyped code to be typed. The programmer would inspect the annotations manually and fix any inaccurate ones, and then run the type checker.
[ Parent
| on HN ]
I'm far from an expert on this, but F# has no requirement for all forms to be explicitly typed, so I'm a bit puzzled as to why this is hard.
Re:Why we're supporting Typed Clojure
by ambrosebs on Saturday September 28, 2013 @02:52AM
(#6461175)
Typed Clojure's type system is too rich to avoid top-level annotations. It's a similar situation to Scala.
I believe it has to do with features like subtyping and method overloading which cause havok for global type inference. Found a paper here: http://ropas.snu.ac.kr/lib/dock/HoMi1995.ps