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
Skip overload resolution when positional arguments have no type information
When a multi-overload method is called with an empty (untyped) positional
argument, we cannot determine which overload to select. Previously, empty
vertices matched all overloads via the found_any mechanism in typecheck,
which caused infinite oscillation in cyclic patterns like:
@x = Foo.transform(@x) # transform has disjoint overloads
The cycle was: empty -> all match -> types flow in -> mismatch -> types
removed -> empty -> repeat forever.
Fix: in resolve_overloads, if any positional argument vertex is empty,
skip overload resolution entirely and return untyped. Dependency edges
are still added so the box re-runs when arguments later receive types.
This is stateless (no flags on boxes or vertices), naturally convergent,
and semantically correct: we cannot dispatch on what we do not know.
Trade-off: passing untyped to an overloaded method now returns untyped
instead of the union of all return types. This affects 4 existing tests.
Single-signature methods (force=true) are unaffected.
0 commit comments