LANG: \Mod::fn(x)\ value call unwired in expression position (\.\-form fixed by #253; \::\ residual) #249

Activity

1. hyperpolymath

   changed the title [-]Qualified-value resolution unwired post-#228: `use Mod;` + `Mod.fn(x)` value call fails before codegen[/-] [+]LANG: \Mod::fn(x)\ value call unwired in expression position (\.\-form fixed by #253; \::\ residual)[/+] on May 19, 2026
2. hyperpolymath commented on Jun 11, 2026

   

   hyperpolymath

   on Jun 11, 2026

   Last edited by hyperpolymath

   OwnerAuthor

   More actions

   Verification 2026-06-11 — closing recommended

   Re-probed against affinescript HEAD (post-#523):

   Probe	Result
   use Mod; Mod::fn(x) (UpperCase head)	✅ Type checking passed
   use mod; mod::fn(x) (lowercase head — covered by #523 / #448 item 1)	✅ parses + type-checks
   End-to-end: use math; math::abs(-5) + Deno-ESM compile + deno run	✅ runs; emitted JS strips the qualifier (const x = abs(-5);)
   Int::to_string(n) / String::len(s) (builtin-type qualified)	✅ parses + resolves (line 920-948 of parser.mly)

   The :: value-call form is wired end-to-end:

   • Parser (parser.mly:909 INT-01 follow-up): upper_ident COLONCOLON lower_ident → ExprField (ExprVar Mod, lower_ident), plus the builtin-type variants at lines 920-948 and the lowercase-head extension from feat(parser): accept lower_ident head in qualified_type_name (closes #448 item 1) #523.
   • Resolver (Resolve.lower_qualified_value_paths, INT-01: cross-module WASM import emission (substrate) #178/feat(resolve): INT-01 — wire qualified-value path use Mod; Mod.fn(x) #253): rewrites ExprField(ExprVar m, fld) → ExprVar fld when m is an ImportSimple qualifier — handles both .-form and ::-form identically.
   • Codegen: emits a bare reference (no JS-side module access required), so the runtime call lands on the imported binding directly.

   Remaining adjacent gap (NOT this issue)

   Multi-segment qualified value paths like Mod::Sub::fn(x) still parse-error:

   pub fn f() -> Int { Mod::Sub::fn(1) }   # parse error at col 26
   use Mod::Sub; ...                        # parse error at col 8 (the second ::)
   

   That's the same adjacency tracked in #448 items 2-3 (multi-segment use, brace-list at multi-segment depth), which was closed earlier as a deferred-by-design slice. If multi-segment value paths become a blocker for a real consumer port, file a fresh issue scoped to that specifically.

   Separately observed during the probe: math::min_int resolved-error because min_int isn't pub-marked on the current HEAD of stdlib/math.affine. That gap is what affinescript#546 (the pub-mark sweep for io/math/option/result/testing) closes — orthogonal to #249.

   Recommendation

   Close #249. The single-segment Mod::fn(x) value-call form this issue tracks is fully wired and regression-locked by the "E2E Qualified Value #178" suite.

   🤖 Cross-estate AS-status sweep on 2026-06-11.
3. hyperpolymath

   added

   bugSomething is broken or behaves incorrectlySomething is broken or behaves incorrectly

   on Aug 27, 2026
4. hyperpolymath commented on Sep 19, 2026

   

   hyperpolymath

   on Sep 19, 2026

   OwnerAuthor

   More actions

   Closing — verified delivered, and this issue's own thread already recommended it.

   The 2026-06-11 comment on this issue is titled "Verification 2026-06-11 — closing recommended" and carries a probe table: use Mod; Mod::fn(x) → Type checking passed; the lowercase-head variant (post-#523) parses and type-checks; end-to-end use math; math::abs(-5) compiles to Deno-ESM and runs. The close was never actioned.

   Re-verified today on main:

   • lib/resolve.ml:975 — lower_qualified_value_paths, the lowering this issue tracks.
   • test/test_e2e.ml — the suite is present and wired: "use Mod; Mod::fn(x) resolves (INT-01: cross-module WASM import emission (substrate) #178 follow-up)" and "use Mod as M; M::fn(x) resolves (INT-01: cross-module WASM import emission (substrate) #178 follow-up)", plus test/e2e/fixtures/cross_caller_qualified_colon.affine carrying the :: form explicitly.

   Both options the issue weighed were settled in favour of (a) accept Pkg::fn in expression position and fold it into the same lowering — that is what shipped. The .-form was fixed in #253 and the :: residual is now closed with it.
5. hyperpolymath

   closed this as completedon Sep 19, 2026