Hacker GitHub

← All repos

tc39/proposal-type-annotations

View on GitHub ↗ ★ 4,388 JavaScript

ECMAScript proposal for type syntax that is erased - Stage 1

82 mentions on Hacker News by 66 people: 5 stories, 77 comments · first 2022-03-09 · latest 2026-05-22

Mentions per year 82 mentions · busiest year 2022 (24)
20082026
  1. …there is a Stage 1 proposal to take the Python/Ruby approach of bringing them into the language: https://github.com/tc39/proposal-type-annotations Were that to happen, that proposal doesn't apply any type checking semantics for the…
    comment by WorldMaker · 2023-03-16 · in TypeScript 5.0
  2. …in Javascript, that would allow the browser to handle TS/Flow files without needing a compile step: https://github.com/tc39/proposal-type-annotations (That's only to allow the type annotations to be there, not to have static checking in…
    comment by whstl · 2023-03-02 · in You don't need a build step
  3. …I know there's JSDoc but the normal syntax is so much better. EDIT: Looks like there's a proposal: https://github.com/tc39/proposal-type-annotations
  4. …that) matters. If it can't run, unaltered, in a Javascript interpreter it isn't Javascript. [0] https://github.com/tc39/proposal-type-annotations
    comment by krapp · 2023-01-20 · in Pipe Operator (|>) For JavaScript
  5. …and the JavaScript Type Annotations Proposal [1] gives me faith that we will grow past TS. [1] https://github.com/tc39/proposal-type-annotations
    comment by the42thdoctor · 2023-01-13 · in Ask HN: Is TypeScript worth it?
  6. …:) If you want to follow along, the proposal to allow type syntax to be part of JavaScript is here: https://github.com/tc39/proposal-type-annotations (To repeat Daniel, there is still a huge amount of work ahead)
    comment by robpalmer · 2023-01-13 · in Ask HN: Is TypeScript worth it?
  7. …expect this to happen. There's a stage 1 ES proposal for allowing TS-like syntax in the browser: https://github.com/tc39/proposal-type-annotations So there's good reason to believe this may actually happen in the next couple of years.
    comment by mark_and_sweep · 2023-01-12 · in Ask HN: Is TypeScript worth it?
  8. …normal JS syntax: (in the same way python PEP 484 – Type Hints are considered optional type hints) https://github.com/tc39/proposal-type-annotations Deno on the server side is pretty cool and uses https://swc.rs/ (Speedy Web Compiler) -…
    comment by ElectricalUnion · 2023-01-05 · in Why is the JavaScript ecosystem like this?
  9. …in that Stage 1 proposal mind you: no one is expecting runtime type hints in the near future.) [1] https://github.com/tc39/proposal-type-annotations
    comment by WorldMaker · 2022-11-14 · in Deno 1.28: Featuring 1.3M New Modules
  10. …features that might not be supported by the target JS version. The "Type Annotations" proposal ( https://github.com/tc39/proposal-type-annotations ), IIRC championed partly by the TS team, will allow type annotations with…
  11. > There's even the future possibility of much of its type syntax being absorbed back into JavaScript: https://github.com/tc39/proposal-type-annotations ... as comments. Which superficially resemble the syntax of type hints but do nothing.…
  12. …There's even the future possibility of much of its type syntax being absorbed back into JavaScript: https://github.com/tc39/proposal-type-annotations
    comment by olitech · 2022-10-09 · in TypeScript is now officially 10 years old
  13. > I even don't understand why browser don't start to work on supporting it directly https://github.com/tc39/proposal-type-annotations
    comment by azangru · 2022-09-29 · in ReScript 10.0
  14. …feature in certain situations, but I don't think it will happen, for back-compat reasons. [1] https://github.com/tc39/proposal-type-annotations
    comment by _greim_ · 2022-06-13 · in Aleph.js – Fullstack Framework in Deno
  15. ▲ 129
    TC39 Proposal: Type Annotations
    story by rglover · 2022-06-08 · 163 comments
  16. …somewhat in that direction: - https://devblogs.microsoft.com/typescript/a-proposal-for-typ... - https://github.com/giltayar/proposal-types-as-comments/
  17. …be a strict subset of TypeScript—or at the very least future compatible—for this very reason. 1. https://github.com/giltayar/proposal-types-as-comments
    comment by runarberg · 2022-03-17 · in Deno Is Webby
  18. Some FAQ items address this: https://github.com/giltayar/proposal-types-as-comments#why-n... Various good reasons, like how it would hinder TS evolution and you'd end up having to compile TS to whatever older version of TS the slowest…
    comment by hombre_fatal · 2022-03-12 · in ECMAScript Proposal: Types as Comments
  19. ▲ 65
    ECMAScript Proposal: Types as Comments
    story by 0xedb · 2022-03-12 · 36 comments
  20. ▲ 2
    ECMAScript Proposal: Types as Comments
    story by mceachen · 2022-03-11 · 1 comment
  21. …that people seem to be asking here, so I'd recommend people to take a look at that instead: https://github.com/giltayar/proposal-types-as-comments/ Also the announcement: https://devblogs.microsoft.com/typescript/a-proposal-for-typ... And…
  22. …major shift; and I'm not sure the proposers have even considered the ramifications of it. [1] https://github.com/giltayar/proposal-types-as-comments/
  23. …static typing, they are not supersets of JavaScript, and thus are not relevant to this proposal. https://github.com/giltayar/proposal-types-as-comments/#what...
  24. …to change type semantics later on. https://devblogs.microsoft.com/typescript/a-proposal-for-typ... https://github.com/giltayar/proposal-types-as-comments/
  25. ▲ 2
    Hijacking ignored type annotations for other features
    story by tolmasky · 2022-03-10 · 0 comments
  26. …or a good architecture. If its behind this feature request is a different pain to be solved. [1] https://github.com/giltayar/proposal-types-as-comments/#comm...
  27. ▲ 5
    ECMAScript Proposal: Types as Comments
    story by ingve · 2022-03-10 · 0 comments
  28. As the FAQ of the proposal mentions ( https://github.com/giltayar/proposal-types-as-comments/#FAQ ), we believe adding runtime type checking would be untenable. This stems from both performance concerns and concerns around evolving…
    comment by DanRosenwasser · 2022-03-10 · in A Proposal for Type Syntax in JavaScript
  29. …proposed here. There is some information on the FAQ about why runtime types are a non-starter. ( https://github.com/giltayar/proposal-types-as-comments/#why-... ) This comment probably won't count for much - actions speak louder than…
    comment by DanRosenwasser · 2022-03-09 · in A Proposal for Type Syntax in JavaScript
  30. The FAQ addresses this: https://github.com/giltayar/proposal-types-as-comments#shoul... https://github.com/giltayar/proposal-types-as-comments#shoul... The idea is to avoid hampering competition, evolution, and innovation in the…
    comment by robpalmer · 2022-03-09 · in A Proposal for Type Syntax in JavaScript
  31. …courage to undertake it! Edit: no it's not [1], though I'm still not sure what it does mean. [1] https://github.com/giltayar/proposal-types-as-comments#type-...
  32. https://github.com/giltayar/proposal-types-as-comments/#why-... > Why not define a type system for JS in TC39 instead? > TC39 has a tradition of programming language design which favors local, sound checks. By contrast, TypeScript's model…
    comment by dfabulich · 2022-03-09 · in A Proposal for Type Syntax in JavaScript