proposal-composites

They were going to do this with Records and Tuples but that got scrapped for reasons I’m not entirely clear on. It appears a small proposal along these lines has appeared in then wake of that called Composites[0]. It’s a less ambitious version certainly. [0]: https://github.com/tc39/proposal-composites

> it is obviously an ES runtime thing, but it is simply weird to have to reason about objects being essentially the same but different—and if memoization allows me to not have to do it and, with some discipline, make it safe to assume that (() => true) is the same as (() => true), why pass on that opportunity? it sucks both ways - the default is that stuff is different if it looks the same so you can't not do anything, but the only solution is both a lot of work and really easy to mess up completely. The TC39 Composites proposal[1] would be a great step in the right direction, but it will take years in the best scenario, there's really no guarantee that React will take advantage of it, and it still leaves out a lot of cases (Dates, to name one) [1]: https://github.com/tc39/proposal-composites

> If the Records and Tuples proposal were progressing, JSX could maybe create Records with boxes, but that proposal has been stalled, especially on the record identity and box parts that 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