You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the Records & Tuples proposal was withdrawn at the TC39 plenary on 14 April 2025 and the Composites proposal covers many of the same use cases, i'm curious about the future of JSON.parseImmutable. Should this proposal be archived alongside Records & Tuples, is there a plan to adapt it using Composite, or should it remain on hold until a proposal with immutable structures reaches Stage 3?
The text was updated successfully, but these errors were encountered:
One option is that the API returns regular objects, no different to Object.freeze but with the potential efficiency compared to JSON.parse and then doing a manual traversal to freeze.
Another option would be to adapt it to use Composite, though we'd have to wait to see how that proposal evolves.
Since the Records & Tuples proposal was withdrawn at the TC39 plenary on 14 April 2025 and the Composites proposal covers many of the same use cases, i'm curious about the future of
JSON.parseImmutable
. Should this proposal be archived alongsideRecords & Tuples
, is there a plan to adapt it usingComposite
, or should it remain on hold until a proposal with immutable structures reaches Stage 3?The text was updated successfully, but these errors were encountered: