[ETS] Preserve TypeScript structural object types - #363
Open
CaelmBleidd wants to merge 5 commits into
Open
Conversation
Contributor
CaelmBleidd
force-pushed
the
caelmbleidd/native-ts-call-targets
branch
from
August 21, 2026 15:32
7884d06 to
80a8a9b
Compare
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
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.
What changed
TYPE_LITERALclasses instead of degrading them toUnknownType. Field names, field types, modifiers, optional markers, and recursive references are retained.objectkeyword as an empty structuralTYPE_LITERALclass.Type literals containing unsupported or computed members still fall back to
UnknownTypeas a whole, so the frontend does not expose a misleading partial shape.Why this is needed
The native TypeScript frontend should preserve source type information without imposing runtime interpretation policy on downstream analyses. Previously, structural annotations lost their fields, imported structural types could be emitted more than once with the same signature, and generic shapes could be specialized by whichever use site happened to be lowered first.
The emitted EtsIR now has one stable, declaration-owned structural entity, while each use carries its own type arguments. Type-level anonymous structures (
TYPE_LITERAL) remain distinct from runtime object literals (OBJECT).Verification
npm test: 212 frontend tests passed.npm run build: TypeScript checking, bundling, and runtime packaging passed.:usvm-ts:test;:usvm-ts-dataflow:test.