What are Types? Kinds? Constraints? Propositions? Are these always values?
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
I think it's nicer when types and kinds can be manipulated with the same operational semantics (and even syntax!) we use for normal values. Haskell at least now has DataKinds. Scala had path-dependent types since very early, but it's really bulky to use.
Yes, but the more freedom you have to manipulate them arbitrarily, the less freedom you have to reason about them quickly... it's definitely a trade-off! :)
-
-
I think we have to be careful about this meta-argument. We want the freedom to make constraints! Conversely, we don't want constraint from making constraints. And this is why I really want more unification of values, types, kinds, etc.
-
But my argument is that by unifying everything to the most general, we lose the advantages we get from constraints, e.g. being able to do declarative type calculations without run-like evaluation, and having tooling which supports that.
- Show replies
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.