Strictly Tagged Clojure
arrdem.com
arrdem.com
Not sure what that means, thought Clojure was a dynamically typed language with optional static types (via Clojure.Typed). If it were statically typed then it would not blow up at run time when you, for example, mke a typo.
Personally I find Clojure.Typed code far more readable, not to mention the added safety/performance. Any chance that will become the default? A statically typed Clojure + ClojureScript would be pretty compelling ;-)
I believe core.typed has no effect -- neither positive nor negative -- on performance. AFAIK, it doesn't affect code generation in any way.
Interesting, assumed otherwise. Groovy, another dynamic language with optional static typing, does benefit performance-wise when electing to use the `@CompileStatic` annotation on applicable code blocks.
A Clojure.Typed with performance improvements would certainly benefit projects like Storm. Probably a ton of work involved though, otherwise it would have been done already.
Hope this helps.
Since Groovy 2, however, the `@CompileStatic` annotation has been available. It's not being used much, probably because people using Groovy just use it for scripting, e.g. testing Java code or in Gradle build scripts. Because only one programmer built it, many developers are concerned about residual bugs, and just use Java or Scala instead.
While not statically typed, Clojure is an aggressively dynamically checked language.
;; clojure
(let [colour :red] (f color))
will throw a compile-time error, whereas # python
colour = "red"
f(color)
will only show up at runtime. That makes a big practical difference.