fix: type verification panic for uncaptured recursive tagged alternations #280
Conversation
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
zharinov
force-pushed
the
fix/recursive-tagged-alt-type
branch
from
c77923d to
17172fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Q = (Rec)whereRecis a recursive tagged alternation — now correctly infersQ: Recinstead ofVoidEndEnumeffect placement in named nodes with children — effects now execute after children complete, not after matching the parentReftypes in bytecode emissionWhy
cargo run -p plotnik-cli -- exec -q 'Rec = [...] Q = (Rec)' ...panicked with type verification mismatch: runtime produced tagged union output but type system expectedVoid. Three interconnected bugs needed fixing to resolve this.