Skip to content

Store TypeScript void results as undefined values - #503

Merged
CaelmBleidd merged 1 commit into
caelmbleidd/pr479-retain-stopped-ts-statesfrom
caelmbleidd/pr479-ts-void-storage
Oct 14, 2026
Merged

CaelmBleidd merged 1 commit into
caelmbleidd/pr479-retain-stopped-ts-statesfrom
caelmbleidd/pr479-ts-void-storage

Conversation

@CaelmBleidd

Copy link
Copy Markdown
Member

Assigning the result of a void method can fail because EtsVoidType has no storage sort. Map it to address storage, matching the runtime undefined value, so the call's mutation remains observable and its assigned result is undefined.

Extracted from #479 at 421dd926ee39312ec678bfc23be5390066f5a398. Base: #502. The own diff is two production lines and the source-level regression fixture/test.

Validation: VoidAssignment passed (1 test). Full suites are left to CI.

@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pr479-ts-void-storage branch from 52c73ce to 80b1205 Compare October 14, 2026 15:46
@CaelmBleidd
CaelmBleidd force-pushed the caelmbleidd/pr479-retain-stopped-ts-states branch from 34752e5 to 1352314 Compare October 14, 2026 15:46
@CaelmBleidd
CaelmBleidd merged commit 1416a0d into caelmbleidd/pr479-retain-stopped-ts-states Oct 14, 2026
13 checks passed
@CaelmBleidd
CaelmBleidd deleted the caelmbleidd/pr479-ts-void-storage branch October 14, 2026 15:59
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