Hacker GitHub

← All repos

tc39/proposal-record-tuple

View on GitHub ↗ ★ 2,526 HTML archived

ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!

47 mentions on Hacker News by 42 people: 5 stories, 42 comments · first 2019-12-19 · latest 2026-07-31

Mentions per year 47 mentions · busiest year 2021 (11)
20082026
  1. …Java, but much of its basic syntax still resembles Java, so I think it's fair to compare them. [0]: https://github.com/tc39/proposal-record-tuple
  2. …would make it suitable for a JSX semantics. That proposal hasn’t just stalled, it’s been withdrawn. https://github.com/tc39/proposal-record-tuple/issues/394 It has been replaced by https://github.com/tc39/proposal-composites
    comment by llcooliovice · 2025-06-27 · in The time is right for a DOM templating API
  3. …with good DX is JavaScript. Also, it would be nice to have `Node.prototype.insertAfter()` :) 1. https://github.com/tc39/proposal-record-tuple
    comment by localvoid · 2025-06-27 · in The time is right for a DOM templating API
  4. …affects pattern matching, though I'm not sure why. I'm much less up to date on that proposal. [1] https://github.com/tc39/proposal-record-tuple/issues/387
    comment by rimunroe · 2025-01-30 · in JavaScript Temporal is coming
  5. …be asking "is it deeply immutable?" or even checking its shape rather than "is it a record?". [0] https://github.com/tc39/proposal-record-tuple/issues/390#iss... [1] https://github.com/tc39/proposal-record-tuple/issues/292#iss... [2] If…
    comment by maxdamantus · 2024-10-11 · in Proposal: JavaScript Structs
  6. …massive wall of text, but I think it's hard to capture the various trains of thought concisely. [0] https://github.com/tc39/proposal-record-tuple/issues/387#iss... [1] https://github.com/tc39/proposal-record-tuple/issues/292#iss... [2]…
    comment by maxdamantus · 2024-10-11 · in Proposal: JavaScript Structs
  7. …reason to use var any more. I feel similarly about the proposals to introduce records and tuples: https://github.com/tc39/proposal-record-tuple ... in most scenarios you'll probably be better off using records rather than objects, and…
    comment by afavour · 2024-10-10 · in Proposal: JavaScript Structs
  8. …use workers switched to Webassembly. Talking about JS proposals, I'm looking forward to this one: https://github.com/tc39/proposal-record-tuple Records and tuples can make a lot of logic much more easier to read, and way less fragile. Not…
    comment by egeozcan · 2024-10-10 · in Proposal: JavaScript Structs
  9. …big step is dependent on JS language/runtime features. Specifically the Record-Tuple proposal ( https://github.com/tc39/proposal-record-tuple ) TL;DR: It's a way to designate data as being immutable. JS doesn't currently have a good way to…
  10. There is a years-old proposal for deeply-comparable types: https://github.com/tc39/proposal-record-tuple Maybe we'll see it one day.
    comment by tobz1000 · 2024-06-25 · in New JavaScript Set Methods
  11. relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387 and which shows that a symbol based protocol was the kind of approach that could've worked from the start. See…
  12. You mean like this stage 2 proposal? https://github.com/tc39/proposal-record-tuple
  13. …the situation with "Records and Tuples" [0], but it's been stuck in committee hell for years. [0] https://github.com/tc39/proposal-record-tuple
  14. …a deep comparison. If I am not mistaken, Records/Tuples are in fact strictly limited to this case: https://github.com/tc39/proposal-record-tuple#jsonstringify So basically there is no difference to having a function serialize() that just…
    comment by moritzwarhier · 2024-01-07 · in The Everything NPM Package
  15. …“deep path properties” syntax which allows for efficient and ergonomic immutable updates: - https://github.com/tc39/proposal-record-tuple - https://github.com/tc39/proposal-deep-path-properties-for-re...
    comment by namuol · 2023-12-22 · in Deep cloning objects in JavaScript
  16. …class based version of this, that is stage one, for adding structs[2]. They behave similarly. [0]: https://github.com/tc39/proposal-record-tuple [1]: https://github.com/tc39/proposal-record-tuple/issues/10 [2]:…
    comment by no_wizard · 2023-01-20 · in Pipe Operator (|>) For JavaScript
  17. …there's an active proposal to add deeply immutable objects and arrays: records and tuples. [0] [0]: https://github.com/tc39/proposal-record-tuple/
  18. …Repo lists that proposal as currently Stage 2. Appears to be under active review for Stage 3: https://github.com/tc39/proposal-record-tuple/issues/336
    comment by WorldMaker · 2022-10-04 · in The TC39 Process
  19. There's a JavaScript stage-2 proposal for records and tuples: https://github.com/tc39/proposal-record-tuple
    comment by davidkunz · 2022-08-29 · in ValueObject (2016)
  20. …that will fix this problem by introducing records and tuples like python (immutable objects/arrays) https://github.com/tc39/proposal-record-tuple but it still seems far off to being usable as I don't think it will be viable to polyfill it…
    comment by DanielHB · 2022-08-17 · in Why React Re-Renders
  21. …world. And as a direct influence, JS will adopt immutable data structures – tuples and records. https://github.com/tc39/proposal-record-tuple
    comment by mlajtos · 2022-08-17 · in Why React Re-Renders
  22. …proposal advances to stage 3 we'll finally have native immutable data structures in JS [1]. [1] https://github.com/tc39/proposal-record-tuple
  23. …immutable data structures (record + tuples) proposal to land, this one is of much more value IMO https://github.com/tc39/proposal-record-tuple
    comment by cphoover · 2022-06-08 · in TC39 Proposal: Type Annotations
  24. …React. I'm very excited about Records and Tuples in JS to help with the immutability, for example: https://github.com/tc39/proposal-record-tuple
  25. …operator. When the time comes I'll be curious to see if there's any progress on that front. [1] https://github.com/tc39/proposal-record-tuple
  26. Immutability is the whole point of records and tuples. You can read more about them on the proposal: https://github.com/tc39/proposal-record-tuple .
    comment by Zababa · 2021-12-13 · in Deno Joins TC39
  27. Record and Tuple are actively being worked on: https://github.com/tc39/proposal-record-tuple -- currently Stage 2.
    comment by dten · 2021-12-13 · in Deno Joins TC39
  28. Immutable data structures are on the agenda over in https://github.com/tc39/proposal-record-tuple and I would vote for that in Deno while I have the chance.
    comment by wiredearp · 2021-12-13 · in Deno Joins TC39
  29. There's a proposal for immutable records and tuples: https://github.com/tc39/proposal-record-tuple Theoretically they would use structural sharing for their implementation which should reduce the overhead of creating a whole new array of…
    comment by richeyryan · 2021-11-08 · in Scripting languages of the future
  30. …are proposed immutable data structures and currently in stage 2[1] (same as the pipe operator). [1] https://github.com/tc39/proposal-record-tuple
    comment by graftak · 2021-09-14 · in TC39 Pipeline Operator – Hack vs. F#
  31. …(record and tuple [0]) for example. Current FP story in ts/flow is surprisingly good. [0] https://github.com/tc39/proposal-record-tuple
  32. Tuples are coming to JS: https://github.com/tc39/proposal-record-tuple#tuple
    comment by bpierre · 2021-08-20 · in A Visual Guide to React Rendering
  33. https://github.com/tc39/proposal-record-tuple Only stage 2, so whether it'll get through to next stage is up in the air, will depend on interest (compare to Temporal which started fairly slow but has gained huge momentum recently and is…
    comment by RobertKerans · 2021-07-13 · in Elm Compiler Written in Elm
  34. There is an active TC39 proposal to add immutable types to JS: https://github.com/tc39/proposal-record-tuple
    comment by nahuel0x · 2021-03-09 · in Immutable Approaches
  35. …function of their own to avoid polluting own-property-keys/name clashes with other libraries). [1] https://github.com/tc39/proposal-record-tuple
  36. …arrays. On this subject specifically, see the records & tuples proposal (currently at stage 2): https://github.com/tc39/proposal-record-tuple
  37. …osoft/TypeScript/pull/12253#issuecomm... [3] https://github.com/microsoft/TypeScript/issues/12936 [4] https://github.com/tc39/proposal-record-tuple
  38. Seems like a lot of options were/are debated: https://github.com/tc39/proposal-record-tuple/issues/10 The benefit to #{}/#[] is that # is not an existing identifier character (other than private fields) in JS, and also isn't an existing…
  39. …languages, the immutable bits didn't register. Sorry. Reading the proposal (TC39) explains all. https://github.com/tc39/proposal-record-tuple Paraphrasing, if I understand TC39 correctly, an immutable map is a record and an immutable array…
  40. …attribute/children structure we need for markup. [1]: https://lit-html.polymer-project.org/ [2]: https://github.com/tc39/proposal-record-tuple [3]: https://github.com/samuelgoto/proposal-block-params
  41. …better handling of objects, the gap between it and clojure will very small for most daily tasks. https://github.com/tc39/proposal-record-tuple https://github.com/tc39/proposal-object-iteration
  42. …and tuples to the system. Since they cannot be modified, the general performance will go up. https://github.com/tc39/proposal-record-tuple I like the idea of types, but dislike typescript. Most importantly, it is not a sound type system…
    comment by hajile · 2019-12-19 · in State of JavaScript 2019