Designing type inference for high quality type errors
Type inference has a reputation for causing unhelpful error messages from the compiler when there is a type error. For example, here’s a typical comment:
I started a project at work with flowjs, got inscrutable type errors in a different file than wherever the root cause was and bailed for typescript.
However, things don’t have to be this way. Type inference’s bad reputation is due to design decisions in existing languages that sacrifice good error messages in exchange for other goals. There is ...
Read more at blog.polybdenum.com