You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 06fc7ff
Browse filesBrowse the repository at this point in the historyBrowse files
format: make invoke.target optional for internal calls (#242)
Internal calls via JUMP normally carry a code pointer to the callee's
entry point, but there isn't always a meaningful target to record — e.g.
at the first instruction of an inlined body, where the JUMP has been
elided. The callee identity (identifier, declaration, type) stays
meaningful; the target does not. Same pattern as return.data being
optional.
- Schema: drop `target` from InternalCall.required; expand the
description; add a worked example for the no-target case.
- TS types: mark `target` optional; relax the guard.
- bugc: guard target access in patchInvokeInContext (+ tests assert
target is defined before dereferencing).
Wave 1 of the transform-context → main split (#31): transform-schema-
independent. Forward-references to `transform:["inline"]` in the prose/
example are deferred to the wave that lands the transform schema.
0 commit comments