Emit a diagnostic when using a type as a value

[saulecabrera]

Currently, when using a type as a value, the compiler hits an assert. It should instead emit a diagnostic.

Example

class A {
  a: i32 = 1;
}


function id<T>(p: T): T {
  return p;
}

export function add(): void {
  id<A>({a: i32}); // Note the use of i32
}

Expected
Something similar to:

'i32' only refers to a type, but is being used as a value here.

Actual

Assert

[SebastianSpeitel]

Typescript has two "namespaces". One for types and the other for values and it prevents using types in places where a value is required but in this case i32 actually refers to the namespace (which is a value), that contains the static members of the type.

[saulecabrera]

Good call but I'm less concerned about how TS handles this, I'm more concerned about the current behaviour which is hitting an assert rather than emitting a diagnostic.