The smallest type change make entire APIs incompatible, hence a lot of pain in OCaml: forced upgrades, forced downgrades, crazy version update schedules, extra forks, reluctance to fix bad early choices that would break compatibility, etc. Types DIRECTLY cause library badness.
-
-
True. OTOH, incorrect or imprecise attribution of costs can very easily lead to erroneous design tradeoffs. I believe you conflated a lot of features under 'types' to make your argument. E.g. Why does a design decision for opaque modules or type erasure fall under 'types'?
-
Because, without “types”, you wouldn’t have been early bound to make that decision once and for all your language users for all time relatively early in the evolution of your language (effectively tying their hands and frustrating them needlessly)?
End of conversation
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!