Potentially unpopular opinion: if you haven't studied type theory, you should not be designing programming languages, because you don't know the span of the design space. Sure, you can hack something together, but you won't know what it's missing or what you got wrong.
-
-
I suspect that if a language has more than a couple of people designing it, it's probably too big to keep in your head, and that's probably bad. See C++ as an exemplar of what not to do. (That said, you do want feedback from a large number of users.)
-
A modern typesystem is enough work for more than one person: complexity and termination of checking or inference, row types, parametricity, co and contra variance, subtyping, inheritance, fixed points, dependencies, linearity, ownership, temporal or epistemic modalities...
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!