Brummel/AILang
1
0
Fork 0
Code Issues 29 Pull Requests Actions Packages Projects Releases Wiki Activity

Split BadCrossModuleTypeRef into two diagnostics #11

New Issue
Open
opened 2026-05-20 13:21:57 +02:00 by Brummel · 1 comment
Brummel commented 2026-05-20 13:21:57 +02:00
Owner
Copy Link
Copy Source

The current single shape collapses unknown-owner and known-owner / unknown-type-in-owner into one message. The two cases suggest different fixes (add (import <owner>) vs. fix the type name). In the known-owner branch, list the owner's available type defs as candidates the way bare-cross-module-type-ref lists candidates from imports.

context: fieldtest 2026-05-11 — examples/ct_3*.ail exhibits both branches with identical-shape diagnostics.

The current single shape collapses unknown-owner and known-owner / unknown-type-in-owner into one message. The two cases suggest different fixes (add `(import <owner>)` vs. fix the type name). In the known-owner branch, list the owner's available type defs as candidates the way `bare-cross-module-type-ref` lists candidates from imports. **context:** fieldtest 2026-05-11 — `examples/ct_3*.ail` exhibits both branches with identical-shape diagnostics.
Brummel commented 2026-06-02 10:26:31 +02:00
Author
Owner
Copy Link
Copy Source

Verified still VALID 2026-06-02. Note: the existing BareCrossModuleTypeRef / BadCrossModuleTypeRef split is a different axis (bare vs qualified reference), not the split this issue asks for. BadCrossModuleTypeRef still collapses the two qualified sub-cases into one { module, name } shape: unknown-owner (crates/ailang-core/src/workspace.rs:1101, prefix not in local_types) and known-owner/unknown-type (workspace.rs:1106, owner exists but lacks the suffix). Neither lists the owner's available TypeDefs as candidates the way the bare path does. The ask stands.

Verified still VALID 2026-06-02. Note: the existing `BareCrossModuleTypeRef` / `BadCrossModuleTypeRef` split is a *different* axis (bare vs qualified reference), not the split this issue asks for. `BadCrossModuleTypeRef` still collapses the two qualified sub-cases into one `{ module, name }` shape: unknown-owner (`crates/ailang-core/src/workspace.rs:1101`, prefix not in `local_types`) and known-owner/unknown-type (`workspace.rs:1106`, owner exists but lacks the suffix). Neither lists the owner's available TypeDefs as candidates the way the bare path does. The ask stands.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Core functionality broken — takes precedence over everything else in the queue. /boss preempts current work to handle it
 bug
Observable misbehaviour — surface inconsistency, false positive, wrong output
 feature
Smaller addition inside a milestone, no full spec
 idea
Not yet decision-ready, no commitment
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/AILang#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?