Skip to content

Fix declared-owner dispatch for super constructors - #475

Merged
CaelmBleidd merged 2 commits into
mainfrom
caelmbleidd/ts-super-constructor-dispatch-20261013
Oct 13, 2026
Merged

CaelmBleidd merged 2 commits into
mainfrom
caelmbleidd/ts-super-constructor-dispatch-20261013

Conversation

@CaelmBleidd

@CaelmBleidd CaelmBleidd commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

A derived constructor calling super() was resolved against the receiver's dynamic class, so the interpreter selected the derived constructor again and exhausted the execution budget without producing results. Resolve direct constructor calls against their declared class and preserve the same derived receiver and arguments. Captured property calls retain their existing function/virtual resolution.

Independent against current main 9f2ac2e; no model, Calls or experiment stack is included. The shared fix also restores the inherited-callback regression in #418.

Review the direct-versus-captured call distinction, exact constructor owner and executable overload selection. Source regressions cover implicit parent construction, explicit super arguments with derived receiver state, and a callable property named constructor.

Validation: the source regression/call gate passed (42 discovered tests, 33 executed, 9 pre-existing skips); final compilation and Detekt main/test passed on 0717623. Full CI run 38344451125 passed on this exact final head. No upstream merge is included.

@CaelmBleidd
CaelmBleidd merged commit 5f535b3 into main Oct 13, 2026
7 checks passed
@CaelmBleidd
CaelmBleidd deleted the caelmbleidd/ts-super-constructor-dispatch-20261013 branch October 13, 2026 08:38
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