Skip to content

[TS] Evaluate computed object-literal property keys - #405

Merged
CaelmBleidd merged 1 commit into
neofrom
caelmbleidd/ts-374-computed-object-keys
Oct 10, 2026
Merged

CaelmBleidd merged 1 commit into
neofrom
caelmbleidd/ts-374-computed-object-keys

Conversation

@CaelmBleidd

@CaelmBleidd CaelmBleidd commented Oct 4, 2026 •

Copy link
Copy Markdown
Member

Computed object keys currently collapse to a placeholder. Emit ToPropertyKeyExpr, generic PropertyRef and ordered data-property definitions, evaluating the key once before the value and preserving the receiver before key coercion. This PR contains the object-key contracts and lowering, without getters, spread copies or destructuring rest.

Validation: fresh typecheck and focused frontend tests (4 passed) on the exact rewritten head. The complete semantic stack at original #425 also passed the frontend build and 622 tests. Rebase preserved the original source tree exactly. Frontend/JSON/model correctness does not establish downstream USVM execution support.

Fixes #374

@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/ts-pointer-receiver branch from 57f95e4 to 50b36cb Compare October 10, 2026 17:28
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/ts-374-computed-object-keys branch from c18ad32 to 0ded336 Compare October 10, 2026 17:29
@CaelmBleidd
CaelmBleidd changed the base branch from caelmbleidd/ts-pointer-receiver to neo October 10, 2026 17:29
@CaelmBleidd
CaelmBleidd merged commit 6961a10 into neo Oct 10, 2026
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

Successfully merging this pull request may close these issues.

1 participant