Repository navigation
[TS] Preserve evaluated computed constructor targets - #406
Merged
Merged
Conversation
CaelmBleidd
force-pushed
the
caelmbleidd/ts-374-computed-object-keys
branch
from
October 10, 2026 17:29
c18ad32 to
0ded336
Compare
CaelmBleidd
force-pushed
the
caelmbleidd/ts-387-computed-new
branch
from
October 10, 2026 17:29
b377280 to
29c8e7c
Compare
CaelmBleidd
changed the base branch from
caelmbleidd/ts-374-computed-object-keys
to
neo
October 10, 2026 17:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Computed constructor accesses currently reject before allocation. Evaluate property/array/tuple constructor targets once, retain optional guards and runtime constructor values, and normalize ClassValueRef to Local for Kotlin decoding. Runtime namespace constructor objects remain explicitly unsupported.
Validation: fresh typecheck and focused frontend tests (2 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 #387