feat: ensure SMIR export records function item types #104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
While exporting SMIR, stable-mir-json fails to record types for closure/function constants. Consumers that rely on lookupTy (e.g., KMIR) therefore fall back to typeInfoVoidType, which eventually produces thunk values and halts execution. This surfaced when running kmir prove-rs/kmir show on interior-mut-refcell.rs.
Changes
Result
The generated *.smir.json now contains the missing function-item types. KMIR no longer falls back to typeInfoVoidType, and the previously stuck proof run completes without emitting thunk.