Terrible error message for calling/constructing types

[DanielRosenwasser]

https://twitter.com/sebmck/status/1141776682275049472

Suggestions

This expression is not callable.
  Type '{0}' has no call signatures.

For unions:

This expression is not callable.
  No constituent of type '{0}' is callable.

This expression is not callable.
  Not all constituents of type '{0}' are callable.
    Type '{0}' has no call signatures.

This expression is not callable.
  Each member of the union type '{0}' has signatures, but none of those signatures are compatible with each other.

The same would be done for constructors.

This expression is not constructable.
  Type '{0}' has no construct signatures.

This expression is not constructable.
  No constituent of type '{0}' is constructable.

This expression is not constructable.
  Not all constituents of type '{0}' are constructable.
    Type '{0}' has no construct signatures.

This expression is not constructable.
  Each member of the union type '{0}' has signatures, but none of those signatures are compatible with each other.

[itsMapleLeaf]

"Constituent" doesn't seem like a commonly familiar word. Maybe "possibility"?

[aleclarson]

Should a separate issue be made for better formatting of complex types?

Also, @sebmck is right that type exploding/expanding/resolving is done too eagerly. VSCode could add a button (in the type error tooltip) to view the fully exploded type. Giving the user only the details they need to solve the problem is better for cognitive load. I just wanted to underline this concern, although I'm sure it's already on the minds of the TypeScript team.

[weswigham]

Yeah, it is, the interactive diagnostics PR implements a framework for similar (expanding bits of error messages, linkifying bits) we just need to sell the vscode team on the UI. :3

[DanielRosenwasser]

Thanks @dragomirtitian!!!!