Underneath TypeScript is JavaScript, and underneath JavaScript is typically a JIT (Just-In-Time compiler). Given JavaScript’s underlying semantics, types are typically reasoned about by “shapes”. These underlying shapes work like TypeScript’s interfaces, and are in fact how TypeScript compares custom types like classes and interfaces.
Consider an expansion of the previous example:
interface Action {
type: string;
}
let a: Action = {
type: ‘literal’
}
class NotAnAction {
type: string;
constructor() {
this.type = ‘Constructor function (class)’;
}
}
a = new NotAnAction(); // valid TypeScript!
Despite the fact that Action and NotAnAction have different identifiers, tsc lets us assign an instance of NotAnAction to a which has a type of Action. This is because TypeScript only really cares that objects have the same shape. In other words if two objects have the same attributes, with the same typings, those two objects are considered to be of the same type.
