3 ms·
> no one wants the client to throw type errors where the untyped code would have actually worked That’s not how TypeScript works. You execute it after erasing
by klysm 10mo ago
> no one wants the client to throw type errors where the untyped code would have actually worked
That’s not how TypeScript works. You execute it after erasing the types.
- antihero 10mo agoUnless you use enums, of course.
- jauco 10mo agoOr constructor property initializers. constructor(public foo: string){} Is a typescript feature.
- ZiiS 10mo agoExactly so all the Browser should do is erase the types. Doing that after you have spent extra time downloading and parsing them is not a useful enough feature to lumber the language with having to get all Browser's to ship each new change.