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 4db7884
Browse filesBrowse the repository at this point in the historyBrowse files
Replay scope-deriving mutators in NodeCallbackScope answers
NodeCallbackScope answers getType()/getNativeType() from the asked
node's stored before-scope, which knows nothing about what a rule
derived locally from the callback scope. filterByTruthyValue() and
filterByFalseyValue() were already recorded and replayed onto the
before-scope, but assignExpression(), assignVariable() and
invalidateExpression() were not — a rule assigning a more specific
type onto its scope read the original stored type right back. The
recorded filters were also lost when the derivation chain passed
through one of the unrecorded mutators.
Record every scope-deriving call in one ordered list (replacing the
separate truthy/falsey lists, whose replay was order-lossy between the
two kinds) and replay it in call order in preprocessScope(). Only
top-level calls are recorded: a mutator implemented via other mutators
resets the list to its caller's view and appends itself, and the
replay re-runs the composition.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K2oPPwjrXy88MUsYekCFQ6
0 commit comments