3 ms·
Not at all. This is the list of problems that exist with an overly slow, early and incomplete type checker. This has nothing to do with optional typing at all.
by rurban 11y ago
Not at all. This is the list of problems that exist with an overly slow, early and incomplete type checker.
This has nothing to do with optional typing at all. It's just the expected problems with an early and slow (2min!) implementation of core.typed.
Other type checkers and inferencers in gradually typed languages don't have these problems, so you cannot generalize.
E.g. Optional types in Common LISP on which Clojure is based on doesn't have these problems. Scala has similar problems, but most other non-JVM based gradually typed languages not.
- progman 11y ago> Not at all. This is the list of problems that exist with an overly slow, early and incomplete type checker. What about Shen on Clojure? http://www.shenlanguage.org http://www.shenlanguage.org
- pathsjs 11y agoUh? Scala is not gradually typed, and in fact does not have these problems at all... :-?
- rurban 11y agoBTW, the author talks about this in his Strange Loop talk here: https://www.youtube.com/watch?v=yG9CffLlXx0 https://www.youtube.com/watch?v=yG9CffLlXx0 There are tons of papers with type checkers in the exact same early state, and how they made it fast and more reliable.