describe does not resolve the canonical type-scoped Type.op form #64

New Issue

2026-06-02T13:23:49+02:00

Brummel commented

2026-06-02 13:23:49 +02:00

From series-step1 fieldtest (friction). ail describe --workspace examples/series_sma.ail Series.push (the canonical type-scoped form per model 0007 §1) fails with no module 'Series' in workspace; only series.push / bare push resolve. describe Series prints the TypeDef but not its op set; builtins lists only the 20 primitives, not library-extension ops. A downstream author who just wrote (app Series.push s v) will type the canonical form first and hit a dead end. Fix: make describe's name resolver try the type-scoped branch (mirroring the call-site resolver), and consider surfacing a type's home-module ops when describing the type. Entry path: plan (tidy).

From series-step1 fieldtest (friction). `ail describe --workspace examples/series_sma.ail Series.push` (the canonical type-scoped form per model 0007 §1) fails with `no module 'Series' in workspace`; only `series.push` / bare `push` resolve. `describe Series` prints the TypeDef but not its op set; `builtins` lists only the 20 primitives, not library-extension ops. A downstream author who just wrote `(app Series.push s v)` will type the canonical form first and hit a dead end. Fix: make describe's name resolver try the type-scoped branch (mirroring the call-site resolver), and consider surfacing a type's home-module ops when describing the type. Entry path: plan (tidy).

Brummel referenced this issue from a commit

2026-06-02 15:57:52 +02:00

test(cli): RED pin for type-scoped describe resolution

Brummel referenced this issue from a commit

2026-06-02 15:57:52 +02:00

feat(cli): resolve canonical type-scoped describe form

Brummel closed this issue

2026-06-02 15:57:52 +02:00

Sign in to join this conversation.