Type Inference? #12
Description
@domenic: Flow departs from TypeScript significantly in its inference abilities, and I could imagine something much more like Flow. (Or, in general, wanting something with stronger inference capabilities, closer to Haskell/ML than Java in the amount of typing it requires.)
@Waldemar: how do you deal with the fact that type inference is a moving target? How do you deal with backwards compatibility? For example, if you start with "no standardized inference rule" how do you avoid breaking compatibility with type checkers when you introduce "some inference rules"? Likewise, if you start with "some inference rules" how do you avoid breaking compatibility when you want to introduce "more inference rules"? For example, versioning is an obvious/trivial solution, but has its taxes.
@Waldemar: can one make inferences based on assignments or usage?