Keep open dispatch results graph-backed - #10740
Draft
rtfeldman wants to merge 2 commits into
Draft
Conversation
rtfeldman
force-pushed
the
issue-10694/unresolved-instantiation-node
branch
from
August 13, 2026 00:16
1274ec1 to
349f235
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Monotype dispatch lowering eagerly materialized every direct parametric low-level result as a TypeId, even for ordinary value mode where the type was unused. This panicked for U64.to_i64_try because its open error-row default must remain in the instantiation graph until final sealing. Keep dispatch result-mode handling graph-native, preserve the Bool check for negated equality using explicit graph owner data, and add regression coverage. Fixes #10694.