-
-
Notifications
You must be signed in to change notification settings - Fork 27
Expose a deterministic typed HIR dump for compiler diagnostics #772
Copy link
Copy link
Open
Labels
discussionIssues that require a technical or community discussion.Issues that require a technical or community discussion.enhancementA request for a new feature or improvement.A request for a new feature or improvement.help wantedThe issue requires extra attention or help from others.The issue requires extra attention or help from others.needs testingIssues that require additional testing or verification.Issues that require additional testing or verification.
Description
Activity
Metadata
Metadata
Assignees
Labels
discussionIssues that require a technical or community discussion.Issues that require a technical or community discussion.enhancementA request for a new feature or improvement.A request for a new feature or improvement.help wantedThe issue requires extra attention or help from others.The issue requires extra attention or help from others.needs testingIssues that require additional testing or verification.Issues that require additional testing or verification.
Motivation
Available debug outputs expose tokens, syntax AST and backend IR but not a deterministic view of TypedProgram facts. Conversion order, computation types and source spans are difficult to inspect independently of LLVM.
Starting points: front/parser/src/hir.rs, src/runner.rs, src/flags.rs.
Scope
Expose a diagnostic typed-HIR dump containing stable expression IDs, resolved/context/result types, ordered conversions and spans. Exclude process pointer addresses and unstable map iteration. This is not the compiled-library format in #165.
Difficulty: medium.
Completion criteria
Design decision needed: Agree on a development-only textual format versus versioned JSON and its compatibility expectations.
Please mention @LunaStev to discuss the design before starting implementation.