Skip to content

What's the plan for JSON.parseImmutable after Records & Tuples withdrawal? #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LiviaMedeiros opened this issue Apr 25, 2025 · 1 comment

Comments

@LiviaMedeiros
Copy link

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?

@acutmore
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants